open each oemxx.inf up with notpad and search for the string "A347bus". it differs on each computer due to differing oem.inf files installed by various hardware drivers.
Page 1 of 1
Need help with Alcohol 120 %
#12
Posted 12 August 2004 - 09:44 PM
I saw your other post that was edited. It didnt work?
#13
Posted 13 August 2004 - 12:23 AM
I am using an almost identical install now as I was with SR-1a.
The only two major differences are that I'm now using NLite,
and SR-2. It is interesting to note that my install does complete
if left alone, despite the nag screen. When it is finished, Alcohol 120%
works fine.
I'm suspecting that this has something to do with SR-2. Perhaps
as Alcohol is installing the virtual CD drivers, it forces a hardware
detection refresh. Windows may be wanting to install drivers for
the virtual CD drive on it's own, despite the fact that there has
already been a driver installed.
I also wonder if this has something to do with the new protocols
of not installing unsigned drivers. Others have noted that the new
Nvidia Forcewave 61.77 drivers (which are currently the only ones
that support DirectX 9.0c) will not slipstream because they are not
signed. I have confirmed this myself.
My current guess is that since Microsoft has decided to make SR-2
the "Security Awareness" release, that they have made driver
installation more restrictive (especially to a slipstream install).
My next step is going to be to make a custom installation package
just for Alcohol. Perhaps something along the line of using InstallRite
which appears to just throw the software in the correct directories
and then patch the registry. Perhaps that can bypass the hardware
detection problem.
But that is for another day. I've got to get some sleep.
The only two major differences are that I'm now using NLite,
and SR-2. It is interesting to note that my install does complete
if left alone, despite the nag screen. When it is finished, Alcohol 120%
works fine.
I'm suspecting that this has something to do with SR-2. Perhaps
as Alcohol is installing the virtual CD drivers, it forces a hardware
detection refresh. Windows may be wanting to install drivers for
the virtual CD drive on it's own, despite the fact that there has
already been a driver installed.
I also wonder if this has something to do with the new protocols
of not installing unsigned drivers. Others have noted that the new
Nvidia Forcewave 61.77 drivers (which are currently the only ones
that support DirectX 9.0c) will not slipstream because they are not
signed. I have confirmed this myself.
My current guess is that since Microsoft has decided to make SR-2
the "Security Awareness" release, that they have made driver
installation more restrictive (especially to a slipstream install).
My next step is going to be to make a custom installation package
just for Alcohol. Perhaps something along the line of using InstallRite
which appears to just throw the software in the correct directories
and then patch the registry. Perhaps that can bypass the hardware
detection problem.
But that is for another day. I've got to get some sleep.
#14
Posted 13 August 2004 - 01:37 AM
This script will install alcohol 120% and dispatch the scsi driver request box.
copy this into notepad and save it as A120.vbs
Change the items after %systemdrive%\install to reflect the location of your copy of alcohol 120%. Call the script from your install.bat or RunOnceEx and it'll automatically click next then finish when that pesky scsi driver thing appears. on slower computers you may need to increase the 9000 to a higher value, and the same with the 12000.
It works by calling the alcohol 120% installer with the silent switch, then waits 12 seconds for it to finish installing and the scsi driver dialogue to appear, presses tab to highlight the next key, then enter to push it, waits 9 seconds for the driver to install, and presses enter again to click finish and dismiss the box.
Set WshShell = WScript.CreateObject("WScript.Shell")
WshShell.Run ("%systemdrive%\INSTALL\CD\A120\setup.msi /qn REBOOT=REALLYSUPPRESS")
WScript.Sleep 12000
WshShell.SendKeys "{TAB}"
WScript.Sleep 1000
WshShell.SendKeys "{ENTER}"
WScript.Sleep 9000
WshShell.SendKeys "{ENTER}"
WScript.Quit
copy this into notepad and save it as A120.vbs
Change the items after %systemdrive%\install to reflect the location of your copy of alcohol 120%. Call the script from your install.bat or RunOnceEx and it'll automatically click next then finish when that pesky scsi driver thing appears. on slower computers you may need to increase the 9000 to a higher value, and the same with the 12000.
It works by calling the alcohol 120% installer with the silent switch, then waits 12 seconds for it to finish installing and the scsi driver dialogue to appear, presses tab to highlight the next key, then enter to push it, waits 9 seconds for the driver to install, and presses enter again to click finish and dismiss the box.
#15
Posted 13 August 2004 - 03:51 AM
what now didnt the a347bus.sys , a347scsi.sys , oem1.inf , oem1.PNF do the trick. More info please you muss edit the winsiff file ???
MCT you are an expert help please
MCT you are an expert help please
#18
Posted 16 October 2004 - 03:13 PM
the .vbs script doesnt work for me for some reason, i get an error
is there anything that needs to be installed for it to work?
is there anything that needs to be installed for it to work?
#19
Posted 09 April 2005 - 12:24 AM
Set WshShell = WScript.CreateObject("WScript.Shell")
WshShell.Run ("setup.msi /qn REBOOT=REALLYSUPPRESS")
WScript.Sleep 12000
WshShell.SendKeys "{TAB}"
WScript.Sleep 1000
WshShell.SendKeys "{ENTER}"
WScript.Sleep 9000
WshShell.SendKeys "{ENTER}"
WScript.Quit
would that work if i ran it from the same directory? if not how can i get it to define %cdrom%?
Share this topic:
Page 1 of 1



Help
Back to top









