[stickfun]

when i use the switch:

start /wait %systemdrive%\install\DTools\daemon.msi Reboot=ReallySuppress /qn

a dialog box comes out asking for installation of SCSI/RAID drivers at the end

how can i fix this?

thanks

[Sponsor]

[Mosselman]

I would install deamon in a vmware or virtual pc and record the installation with winInstall... then I would just compile a installer with winInstall of the complete installation... This is also very usefull when you are installing drivers that arent certified without having to supress the windows protection on it... (am not sure about last bit though, but I havent had any problems so far)...

[MCT]

all i do is use /qn it doesnt reboot on me

& the scsi drivers are a problem, but its been discussed & the work around i believe was 2 include the drivers on your unattended cd, search device drivers forum for answers or even unattended forum

[stickfun]

but the thing is that i DON'T have SCSI/RAID devices.

i think it's from Daemon Tools

do you guys have this problem when installing Daemon Tools?

[SiMoNsAyS]

the virtual dvd drive that installs daemon it's a SCSI one. if you go to device manager you can see a "DTxxxPRT SCSI Controller" (D)aemon (T)ools (xxx) means 3 numbers version (P)o(RT). maybe it's a problem with that version of daemon, i use version 3.46 and my switch:

Quote

daemon.msi Reboot=ReallySuppress /qb-!

[MCT]

I 2 use 3.46

[stickfun]

thanks for that switch.

i'll try it out

and yea, i use 3.46 too.

[stickfun]

not working

oh well, i guess i just have to install it afterwards

[lpl]

It's weird, but i never used to have that problem until recently. I swear i didn't change a thing, it just popped up.

But if I just leave it alone it goes away by itself. and the program still works. The SCSI controller I get is D346PRT. So i say heck it, i've got other things to worry about...

My switch is this :

%cdrom%\install\Daemon\daemon.msi /qb /norestart

[Robpol86]

no, i have the same problem, and i know whats causing it.

i tried just installing dtools exe (not msi) and it did the same thing. so it was obviously a sp2 problem.

the cause is that new option to install drivers from windows update. you have to make it NOT ask you (the top option)

the middle option (always ask) is the default. all i need is the registry tweak so i dont have to do this manually, here ill post a screen so you know what im talking about

Attached File(s)

•  dtools_driver.gif (16.89K)
  Number of downloads: 338

[stickfun]

is it possible to use something like Taskkill to remove it?

it's not as smooth but it should do the trick.

[Robpol86]

no, taskill wont work. windows is just asking you if you want to let it download a better driver from windows update, which is a waste of time because you already have the driver. a registry tweak or a script would fix this

[stickfun]

can anybody help us?

i'm still having this problem.

[Robpol86]

i finnaly found the reg tweak so it wont ask me if i want to windows update. but NOW it asks me to search for the driver (it finds it if i tell it to search..)

WHY all of a sudden does it do this!?!? even doubleclicking the file will prompt me now. before (only adding a reg tweak), if i manually disabled windowsupdate driver search, it didnt prompt at all. now im confused..

if anyone knows how to solve this, plz tell us!

[stickfun]

anybody?

here's the error screenshot:
http://www.msfn.org/...=post&id=172809

maybe this is a glitch in SP2?

[Robpol86]

ewww a 900+ kB bitmap

here i compressed it, so people on 56k can help

yes thats EXACTLY what im getting now, cant get around it...

no its not a glitch in sp2, (with dtools 3.46), it worked perfectly for me. now all of a sudden it doesnt....

Attached File(s)

•  problem.gif (20.04K)
  Number of downloads: 210

[stickfun]

we still need help

i'm going to format soon so i need to figure this out.

[mazin]

Robpol86, on Aug 20 2004, 11:05 PM, said:

yes thats EXACTLY what im getting now, cant get around it...

You can use a JScript script to deal with that screen.

[Robpol86]

i figured out nlite is the cause of this problem. after splitstreaming w/ nlite, and immediatelly making an iso, i didnt have this problem. but if i continued w/ nlite and make it classic install etc, then i ran into this problem.


maby someone might look into this and find out exactly why nlite makes tis happen?

[MCT]

this obviously isnt a "problem" different components cause different things 2 happen, that is why its suggested that u test it specifically for what u need, b4 burning/finalizing your project, so u dont have this happen