Hi there

I've extracted the nforce4 AMD Package. (Deleted NAM.exe)

Then ran the setup with -r switch.

Copied the iss file to the setup directory.

With 7z created a compressed file.

and with a sfx and config.txt (code below) created an exe.

;!@Install@!UTF-8!
RunProgram="Setup -s"
;!@InstallEnd@!

ISS File

[InstallShield Silent]
Version=v7.00
File=Response File
[File Transfer]
OverwrittenReadOnly=NoToAll
[{EFB7D050-CAD2-11D4-B34D-00105A1C23DD}-DlgOrder]
Dlg0={EFB7D050-CAD2-11D4-B34D-00105A1C23DD}-SdWelcome-0
Count=1
[{EFB7D050-CAD2-11D4-B34D-00105A1C23DD}-SdWelcome-0]
Result=1

The new executable works fine. But. There's always a but.

After the installation it reboots. I don't want him to reboot.

Because its in the middle of my runonceEx.

Is there a way to stop the reboot.

Is tried to add some entries to the iss file. Like SdFinished - reboot etc etc.

No luck.

I must say i use bashrats' driverpacks. thus the chipset drivers are installed.

But I question myself of the SW IDE drivers are installed. Cause after the unattended installation my pc freezes a couples of secs when it's busy. After a normal setup of the nforce4 package, all works fine.

Nevertheless I hope someone can help me out.

Nobody ?

I havn't found solution too ... I try with nForce all series package.

It seems to be an IDE package will cause the reboot.

Try ti re-run your install without IDE folder.

Ok. but the IDE package is the important one. I believe its needed if you have a raid set. And I have 2. But I will try and maybe I can found a workaround for the IDE package.

Thx for the work

I have read the "reboot required" or not isn't specified in the .inf file now, it's system which detect if reboot is necessary or not. Perhaps there is way to force to no reboot but I havn't found yet ... Post any results !

I know. Still trying to get it too work

New drivers are out.

Let's give them a try

nForce4 AMD v6.86

new drivers reboots

IMHO, the reboot is initiated by windows pnp mechanism which is detect the IDE require a reboot (and all futures updates will have the problem) ... but how the original setup can reboot later, if we find we have a solution perhaps ...

I agree.

It's frustating.

Maybe there is a solution in the near future.