[r0sWell]

Hi,


here's my problem :


i install Alcohol 120% v1.9.2.1705 using RunOnceEx.cmd :

REG ADD %KEY%\092 /VE /D "Alcohol 120% 1.9.2.1705" /f
REG ADD %KEY%\092 /V 1 /D "%systemdrive%\Hotfixes\Alcohol120\setup.msi /qn REBOOT=Suppress" /f
REG ADD %KEY%\092 /V 2 /D "REGEDIT /S %systemdrive%\Hotfixes\Alcohol120\enregistrement.reg" /f
REG ADD %KEY%\092 /V 3 /D "REGEDIT /S %systemdrive%\Hotfixes\Alcohol120\settings.reg" /f

when RunOnceEx comes to it, a new message box appears because a new SCSI/RAID hardware has been found.
here is a screenshot :



so in fact, it tells me that Windows found a scsi/raid controller (i don't have any scsi drive or raid system), and i have to install it.


Please help me, when i was working on a SP1a splitstream of XP, there was no problem. I think it's when i came to XP SP2 splitstream that i had this problem.
the installation of Alcohol can be at the beginning, middle, or at the end of RunOnceEx.cmd, it doesn't change anything.


Thanks for your help.

[r0sWell]

up




[sorry i didn't place my topîc at the right place. it has been moved.]

[glent]

look here http://www.msfn.org/board/index.php?showto...hol%20vbs&st=10
4th post down i had the exact same problem and that script works great

[r0sWell]

thanks, i'll test it.

i think my pb is relative to nlite (i removed things, but it should be safe).
i'm still working on it.

[Lucius Snow]

I've got the same problem The auto-it script didn't work here. Isn't there any other solution ? Thank you.

[big poppa pump]

Leave it alone and the message will disappear after 30 seconds. I have learnt to live with it. This is basically something to do with SP2.

[Lucius Snow]

Alright, cheers. I'll let it go like this ... I hope we'll find a true solution someday though.

[Lucius Snow]

up

[r0sWell]

one easy way to solve this pb :


in RunOnceEx.cmd i call alcohol120_install.vbs.

in alcohol120_install.vbs i put :

Set WshShell = WScript.CreateObject("WScript.Shell")
WshShell.Run ("%systemdrive%\Softwares\Alcohol120\setup.msi /qn REBOOT=REALLYSUPPRESS")
WScript.Sleep 15000

WshShell.SendKeys "{TAB}"
WScript.Sleep 1000

WshShell.SendKeys "{DOWN 2}"
WScript.Sleep 1000

WshShell.SendKeys "{ENTER}"
WScript.Sleep 1000

WScript.Quit

(just change the path of Alcohol120%

[Astalavista]

guys why not use autoit for it?

[Lucius Snow]

That script didn't work for me.

[r0sWell]

Lucius Snow, on Feb 4 2005, 04:37 PM, said:

That script didn't work for me.

it works for me, that's strange.

or you can try AutoIt Scripts as Astalavista said just before.

[Lucius Snow]

Actually, it worked in VMware but not in real conditions. I guess it's because of the key delays. The speed of installation will be random between different machines. That script can't always work.

[r0sWell]

Lucius Snow, on Feb 4 2005, 05:42 PM, said:

Actually, it worked in VMware but not in real conditions. I guess it's because of the key delays. The speed of installation will be random between different machines. That script can't always work.

so just adjust the delays to match with your computer speed

[Lucius Snow]

r0sWell, on Feb 4 2005, 09:48 AM, said:

Lucius Snow, on Feb 4 2005, 05:42 PM, said:

Actually, it worked in VMware but not in real conditions. I guess it's because of the key delays. The speed of installation will be random between different machines. That script can't always work.

so just adjust the delays to match with your computer speed

Problem is that i use my Unattended CD on several different PC

[Lucius Snow]

Well i'd like to undersand the origin of the problem. Alcohol drivers are both a347*.sys files inside \System32\Drivers. For some reasons, they can't be installed properly at the install (even if we click on Next until the end of the wizard), and so the Device manager points an error to that device. And when i open Alcohol, the virtual CD drivers are detected by Windows. Normally, that doesn't happen.

So there's an issue with a INF (which is ?) and the drivers ... but i don't see what.

[cestpaspossible]

Hi

Here is my script to install Alcohool

I Use the WPI interface


prog[pn]=['Alcohol 120% 1.9.2. Buil 1705']
cmd1[pn]=['%cdrom%\\IAPPS\\Alcohol\\setup.msi /qn REBOOT=SUPRESS']
cmd2[pn]=['REGEDIT /S %cdrom%\\IAPPS\\Alcohol\\register.reg']
cmd3[pn]=['%cdrom%\\IAPPS\\Alcohol\\Lnk.cmd']
dflt[pn]=['yes']
cat[pn]=['Gravure']
pn++

With this command i don't have new window for detecting new hardware.

[ddebacker]

I'm quite sure this has to do with a policy in Windows XP...

It seems that some people (using nLite?) do have the problem while some others don't.

I'm using nLite 0.97b and I do have the same problem. I would like to get rid of it for all softwares once for good (and not write scripts to work around it).

Any pro of the registry settings?

[Lucius Snow]

I don't use nLite except its patched SYSSETUP.DL_ (i may be linked to it).

[Alanoll]

I'm plagued by this as well, but those darn time constraints....

But I'll also look into it as well.