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.

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.

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?

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

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

But I'll also look into it as well.

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

But I'll also look into it as well.

Thank you. Let us know if you find anything.

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

Well i'm almost sure it has something to do with the patched SYSSETUP.DL_ of nLite ....

Ryan's pack makes problem when it's integrated into non-english O.S. On this forum, Jander proposed another way to integrate it :

1.- From the directory svcpack, run:

expand *.ca_ -r *.cat ..\

2.- Delete the dir svcpack.

3.- Replace svcpack.in_ with the original.

4.- Replace SYSSETUP.DL_ with the version modified by nLite.

5.- Unpack and delete SYSSETUP.IN_:

expand SYSSETUP.IN_ SYSSETUP.INF

del SYSSETUP.IN_

6.- Edit SYSSETUP.INF and add under "[ProductCatalogsToInstall]" all the catalogs:

KB834707.cat

etc....

7.- Pack and delete SYSSETUP.INF:

MAKECAB /D CompressionType=LZX /D CompressionMemory=21 "SYSSETUP.INF"

del SYSSETUP.INF

8.- Edit DOSNET.INF and add the catalogs under "[Files]":

d1,KB834707.cat

etc....

and delete:

[OptionalSrcDirs]

SVCPACK

9.- Edit TXTSETUP.SIF and add the catalogs under "[sourceDisksFiles]":

KB834707.cat = 100,,,,,,_x,,3,3

etc....

10.- Check that these files contain this:

DOSNET.INF

d1,RVMUpPck.cab

d1,RVMUpPck.inf

TXTSETUP.SIF

RVMUpPck.cab = 100,,,,,,_x,,3,3

RVMUpPck.inf = 1,,,,,,,20,0,0

Since i use that method, the problem with Alcohol occurs ...

I hope it's an interesting clue.

i made a quick test:

1) install WinSP2 without modification

2) replace SYSSETUP.dll in "system32" and "system32/dllcache" folder with a patched version

3) disable sfc protection when asked by windows

3) install alcohol

Result -> Drivers Box appears !!!!!!!!

So SYSSETUP.DLL must be the cause of the problem

EDIT: no problem when the file is not patched

EDIT2: just a question. Why this file is patched?

Thanks for this confirmation !

I use this patched file to allow the integrations of hotfixes.

I made an AutoIt script wich work for me.

!!! French script !!!!

; ----------------------------------------------------------------------------
; Set up our defaults/Variables
; ----------------------------------------------------------------------------

AutoItSetOption("WinTitleMatchMode", 1)
;Setup file name
$SF= "msiexec /i Alcohol.msi /qn REBOOT=Suppress"


; ----------------------------------------------------------------------------
; Script Start
; ----------------------------------------------------------------------------

Run($SF)
WinWaitActive("Assistant Matériel détecté")
Send("!N")
Send("!S")
Send("!S")
WinWaitActive("Assistant Matériel détecté","Fin de l'Assistant Ajout de nouveau matériel détecté")
Send("{ENTER}")

A similar script was done before but it didn't work very well here :/

I have found a solution though. It's not very clean but it seem to work : At the very beginning of RunOnceEx.cmd, i put a batch files which remplace SYSSETUP.DLL by the original version. Since Alcohol installation comes after, it works fine.

This script is litte bit different. There is no time delay to wait dialog box. So no problem with different machines speed.

nevertheless I do not know which is the best solution.

So SYSSETUP.DLL must be the cause of the problem

mine is not patched and i have same problem so.......

When we think that it is corrected, that is not the cas.

very strange... i hv been installing alcohol120 on my pc month now.

and today i hv your problem.... hahhaaha just would like to mentioned

that i used nlite to integrate my hotfixes

hm....