MSFN Forums > silent install of Alcohol 120% -> new scsi/raid ?

Full Version: silent install of Alcohol 120% -> new scsi/raid ?

MSFN Forums > Unattended Windows Discussion & Support > Application Installs

r0sWell

Sep 2 2004, 08:27 AM

Hi,

here's my problem :

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

CODE

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

Sep 2 2004, 12:03 PM

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

glent

Sep 2 2004, 12:20 PM

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

Sep 3 2004, 04:35 AM

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

Jan 21 2005, 06:35 PM

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

Jan 21 2005, 08:13 PM

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

Jan 22 2005, 10:41 AM

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

Lucius Snow

Feb 4 2005, 07:19 AM

r0sWell

Feb 4 2005, 08:34 AM

one easy way to solve this pb :

in RunOnceEx.cmd i call alcohol120_install.vbs.

in alcohol120_install.vbs i put :

CODE

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

Feb 4 2005, 08:36 AM

guys why not use autoit for it?

Lucius Snow

Feb 4 2005, 08:37 AM

That script didn't work for me.

r0sWell

Feb 4 2005, 08:40 AM

QUOTE (Lucius Snow @ Feb 4 2005, 04:37 PM)

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

Feb 4 2005, 09:42 AM

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

Feb 4 2005, 09:48 AM

QUOTE (Lucius Snow @ Feb 4 2005, 05:42 PM)

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

Feb 4 2005, 10:01 AM

QUOTE (r0sWell @ Feb 4 2005, 09:48 AM)

QUOTE (Lucius Snow @ Feb 4 2005, 05:42 PM)

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

Feb 4 2005, 11:27 AM

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

Feb 4 2005, 01:58 PM

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

Feb 8 2005, 02:13 PM

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

Feb 8 2005, 02:20 PM

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

Alanoll

Feb 8 2005, 02:30 PM

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

But I'll also look into it as well.

Lucius Snow

Feb 8 2005, 03:05 PM

QUOTE (Alanoll @ Feb 8 2005, 02:30 PM)

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.

Lucius Snow

Feb 9 2005, 05:17 PM

QUOTE (Lucius Snow @ Feb 8 2005, 02:20 PM)

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 :

QUOTE

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.

titou2k

Feb 9 2005, 06:16 PM

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?

Lucius Snow

Feb 9 2005, 06:18 PM

Thanks for this confirmation !

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

titou2k

Feb 10 2005, 09:09 AM

I made an AutoIt script wich work for me.

!!! French script !!!!

CODE

; ----------------------------------------------------------------------------
; 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}")

Lucius Snow

Feb 10 2005, 09:12 AM

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.

titou2k

Feb 10 2005, 09:29 AM

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.

muiz

Feb 10 2005, 09:18 PM

QUOTE

So SYSSETUP.DLL must be the cause of the problem

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

titou2k

Feb 11 2005, 04:12 AM

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

Astalavista

Feb 12 2005, 04:42 AM

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....

muiz

Feb 14 2005, 04:09 PM

ha ha ha

just dont touch it it will disapear by its own thats all

iwod

Mar 11 2005, 10:22 PM

QUOTE (titou2k @ Feb 10 2005, 09:09 AM)

I made an AutoIt script wich work for me.

!!! French script !!!!

CODE

Can anyone translate one for english? I mean with english Windows Name so Autoit can auctually work

This is a "lo-fi" version of our main content. To view the full version with more information, formatting and images, please click here.