Alcohol 120% Build 2722

[implodium]

I too managed to get Alcohol working, but there's one other problem.

I install Alcohol at T-13 stage, but it's entry in add/remove programs is BLANK.

I even tried without any silent switches (ie normal setup with GUI) and still no

luck.

I even tried to re-install Alcohol after windows was installed, but all i got was

icon, product name is still missing (it must be my setup, i just can't figure out

HOW it messes up my install).

I want to fix this issue before it gets worse.

NOTE : all other msi-based setups (like acro reader 6 and alanoll's winamp)

install fine.

If needed, i'll post my winnt.sif.

If ANYONE had their Alcohol 120% installed normally during T-13 sequence,

PLEASE report with as many details as possible !

I urge everyone to answer, even with negative answers.

[Mr. Danny]

Sorry to dredge up old topics, but I don't understand half of what yall are saying.

I am new to this website, and i dont know a whole lot about computers.

I dont know if this has been answered yet, but is it possible to install the trial twice? I just need it for a liiiittle longer. If anyone could help a poor newbie, i would be very happy.

[monisriz]

im having the same problem with alcohol's installation...a "new hardware" window pops up during runonceex..

solution #1 (confirmed but not professional) is to just ignore it..dont bother abt it..dont do anything to it..it will disappear by itself after 10-20 seconds..

another solution which maybe possible is to copy off the two files (a347scsi and a347bus) to ur $oem$/$$/system32 on ur UA cd..and *hope* that alcohol will find those two buggers in the system32 dir during installation..im doing that with my current cd..and test it 2mro...

i tried using the above mentioned "driver0=a347 blablabla" but the window popped up still..

im still trying to find a proper way to install these drivers..

one question though..is this problem only occuring to those who use nlite? i used nlite and had alot of problems with compatibility issues..this time im going nlite-less (disc space not an issue)..so lets see...

any suggestions wud be really appreciated since this thing is messing up an otherwise really awesome progress..

[implodium]

im having the same problem with alcohol's installation...a "new hardware" window pops up during runonceex..

solution #1 (confirmed but not professional) is to just ignore it..dont bother abt it..dont do anything to it..it will disappear by itself after 10-20 seconds..

Umm ... Yes, but that's just not the "neat solution", i agree.

However :

1. install alcohol during t-13 sequence (not 100% working on my machine because

of the dreaded add/remove problem , but you should try anyway !).

btw : as a side-effect, you'll have one reboot less to do after install

2. make vb script with sendkeys command (search for example script for BSPlayer

registration, very neat idea). i've seen couple of oem app setups do a

kill-the-unsigned-driver-warning-window (example : sweex webcam).

3. try to find registry tweak that shortens (or completely disables) driver install

dialog box (i'm sure there's one, i've seen hundreds for just about everything).

this tweak should be implemented at t-13 sequence (it will most likely kick-in

after reboot).

NOTE WELL : since you'll install alcohol during runonceex sequence, after

the install completes, re-enable the tweak immediately and allow reboot. this

additional reboot should (as the previous one, when disabling driver dialog box),

kick-in the REGISTRY tweak again.

I hope i haven't overdone it.

    another solution which maybe possible is to copy off the two files (a347scsi and a347bus) to ur $oem$/$$/system32 on ur UA cd..and *hope* that alcohol will find those two buggers in the system32 dir during installation..im doing that with my current cd..and test it 2mro...

That may be enough, though it wouldn't surprise me if window pops up again.

Try to find on the net where windows stores info on available drivers. There must

beone (example : install location of msi setup in hklm\software\uninstall

subkey).

one question though..is this problem only occuring to those who use nlite?

I doubt it.

i used nlite and had alot of problems with compatibility issues..this time im going nlite-less (disc space not an issue)..so lets see...

I did use nlite to save space, but it's primary benefit is automated integration

of RyanVM's pack.

any suggestions wud be really appreciated since this thing is messing up an otherwise really awesome progress..

I know what you mean ...

[Mr. Danny]

ummm...if that was directed towards my question, could you dumb it down a little for me. Like alot. Put it in the tongue of the n00bs.

[implodium]

ummm...if that was directed towards my question, could you dumb it down a little for me. Like alot. Put it in the tongue of the n00bs.

<{POST_SNAPBACK}>

I'm using CMDLINES.TXT in $OEM$ folder to call a batch script. In that batch script

alcohol setup is executed. There is no hardware wizard window popping up and

the alcohol setup's mandatory reboot is done by windows setup anyway.

Since i'm using T-13 sequence to install Alcohol, i'm left with RunOnceEx to do

another neat thing : making alcohol virtual drive available on the first user logon !

The example code segment should be saved as .reg file and imported

during T-13 sequence via REGEDIT /S X:\myfolder\myfile.reg where X: represents

the location of target drive (either system drive or cdrom, but that's OT).

NOTE : The CMDOW command is from RyanVM pack. Here's excerpt from my

registry file :

Windows Registry Editor Version 5.0

[HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\Windows\CurrentVersion\RunOnceEx]
"TITLE"="One-time final system setup"

[HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\Windows\CurrentVersion\RunOnceEx\001]
@="Setting up Alcohol virtual drives"
"1"="CMD.EXE /C CMDOW.EXE /RUN \"%PROGRAMFILES%\\Alcohol Soft\\Alcohol 120\\Alcohol.exe\""
"2"="SLEEP.EXE 5"
"3"="CMDOW.EXE \"Alcohol 120%\" /HID"
"4"="SLEEP.EXE 60"
"5"="CMDOW.EXE \"Alcohol 120%\" /CLS"

Sequence explained line by line :

LINE 1 :

In this line Alcohol is executed as background task. This means that when

Alcohol is run, the execution sequence continues. This is crucial ! If Alcohol is not

started in background, the system will hang indefinitely waiting for Alcohol to exit

(using "startup" switch won't help, i tried). The CMDOW.exe provides this via

/RUN switch.

LINE 2 :

Sleep.exe (not part of RyanVM package !) is needed to pause the execution long

enough so Alcohol is fully up and running. Without this, the next line will fail.

LINE 3 :

Since in line 2 main window pops up, this command hides it. Having all those

app/cmd windows popping up all over the place ain't professional (well, i'm trying

to make it as good-looking as possible).

LINE 4 :

Another crucial command. This is where sequence is paused to allow Alcohol to

fully prepare virtual drive.

LINE 5 :

Alcohol is being closed down and system contiues booting. This line could be

replaced with "TASKKILL /F /IM Alcohol.exe" but that's far too crude and unfriendly

system-wise.

PS : I still haven't worked out how to hide cmd window which pops up when

executing sleep.exe. I'll get around fixing it when i'm done with other boot-stuff.

[Mr. Danny]

Some things I need defined that I dont know the meaning of:

T-13 Sequence

RunOnceEx

How and what is a .reg file

REGEDIT

CMDOW

RyanVM pack

app/cmd windows

If you could explain these terms to me, I would be very happy.

It sounds like you gave a very thorough answer, and I will look into this stuff with as little knowledge as I have right now. If you could help me with these last terms, I MIGHT be able to do it.

THANK YOU!!!

[muiz]

Some things I need defined that I dont know the meaning of:

T-13 Sequence

RunOnceEx

How and what is a .reg file

REGEDIT

CMDOW

RyanVM pack

app/cmd windows

If you could explain these terms to me, I would be very happy.

It sounds like you gave a very thorough answer, and I will look into this stuff with as little knowledge as I have right now. If you could help me with these last terms, I MIGHT be able to do it.

THANK YOU!!!

or you can do some research , and reading on the forum first.

saves you alot of questions like these

[implodium]

or you can do some research , and reading on the forum first.

saves you alot of questions like these

<{POST_SNAPBACK}>

I have to agree. Although explaining would be OK, primary goal of this forum

is to get help for problems/questions that are not covered yet.

I myself have been researching this forum for 2 months and joined it when

i had no other way of solving some problems on my own.

Please look for info at unattened.msfn.org . This is a whole sub-site, devoted

solely to unattedned windows setup.

Carefully follow it's links, they're cleanly organized in sections. If you skip

something, later it will backfire (speaking from my own expirience).

Enough chatter.