Jump to content

Unattended Problem - Device Drivers?


arry

Recommended Posts

Hi all,

I am having a problem where the it says "setup restarting..." after the first reboot and then the screen just sits there blue. Eventually a windows error box comes up (after ages) saying Virtual Memory is too low and will now resize.. it immediately reboots and goes throught the whole thing again ... over & over

same thing happens to me when i use method 2

Link to comment
Share on other sites


Guys with this error, are u using nLite? I tested my cd not until i tried method 2, and got the same rebooting crap. Finally it hit me to try out the iso before the driver packs and walla, same problem. I stopped using nLite and did the slipstreaming and reduction in size manually and then added the driver packs with method two and received no error. This could be an nLite issue. But hey, I dont know much and could be way off base.

-northofnowhere

Link to comment
Share on other sites

I have problem with no restart problem after setup is finish

In "Presetup.cmd" section "Reset DriverPolicy" i changed folloving lines

REM +=======================================================+

REM | Reset DriverPolicy |

REM |-------------------------------------------------------|

reg add "HKCU\Software\Microsoft\Driver Signing" /v Policy /t REG_DWORD /d 1

reg add "HKCU\Software\Policies\Microsoft\Windows NT\Driver Signing" /v BehaviorOnFailedVerify /t REG_DWORD /d 1

reg add "HKLM\Software\Microsoft\Driver Signing" /v Policy /t REG_BINARY /d 01

REM +=======================================================+

into

REM +=======================================================+

REM | Reset DriverPolicy |

REM |-------------------------------------------------------|

reg add "HKCU\Software\Microsoft\Driver Signing" /v Policy /t REG_DWORD /d 1 /f

reg add "HKCU\Software\Policies\Microsoft\Windows NT\Driver Signing" /v BehaviorOnFailedVerify /t REG_DWORD /d 1 /f

reg add "HKLM\Software\Microsoft\Driver Signing" /v Policy /t REG_BINARY /d 01 /f

REM +=======================================================+

because this keys alredy exist in registry and requires confirmation parametar "/f"

so setup now close presetup.cmd and restart normaly.

Link to comment
Share on other sites

thanks.

I forget to thank you for all your free time spend here. :hello:

Another thing:

If the setup freeze or power failure happen, setup go again after restart, but

then section after "start /WAIT setup.exe %*" in the "presetup.cmd" never be execute.

1. "Reset DriverPolicy" never be execute.

2. "Clenup" never be execute.

3. "Reset DevicePath" never be execute.

Will be better put that stuff somewhere in "RunOnceEx" section and execute them after restart.

Link to comment
Share on other sites

Create an account or sign in to comment

You need to be a member in order to leave a comment

Create an account

Sign up for a new account in our community. It's easy!

Register a new account

Sign in

Already have an account? Sign in here.

Sign In Now
  • Recently Browsing   0 members

    • No registered users viewing this page.
×
×
  • Create New...