[hakeem5454]

how do i do step 3(how do i uncab)

[pene]

*deleted*

This post has been edited by pene: 14 July 2005 - 02:52 PM

[a06lp]

evilvoice, on May 9 2005, 08:17 AM, said:

I have also noticed that setdevicepath will only allow %systemroot%\inf as I have tried many other ways to get anything else to work...I ONLY use Ryans Update Pack and this Driver setup...it worked tons of times before, just not anymore...is there something that is possibly stopping this from working?
<{POST_SNAPBACK}>

Hmm, it just hit me that this may be the same problem I have been encountering recently. Can you confirm which RyanVM pack Version started this problem?

Also, did you end up with a solution to this?

[evilvoice]

it was an error in where i ran setdevicepath...I tried different things and did get it working, though with the new rvmpack, I found out that my source was corrupted and have since had to start from scratch. I am not quite at the point to redo this yet, but when I do apply this method back, I will let everyone know problems or successes with it.

[Ixel]

I'm wondering if this method of installing drivers (using the method originally posted by Pyron) works when you install the windows from the hard drive. I run winnt32 with /localsource switch and so setup starts the GUI and copies the necessary files to the hard drive, then goes to text setup, then back to GUI. Will it work doing it this way?

EDIT: To answer my own question and for anyone else who might be interested, it does work. Thanks to Pyron for his work on this.

This post has been edited by Ixel: 28 July 2005 - 09:36 PM

[Sgt_Strider]

hakeem5454, on Jul 13 2005, 08:26 PM, said:

how do i do step 3(how do i uncab)
<{POST_SNAPBACK}>

Good question, how do you uncab?

[Necros]

Hi

Pyron you made an excellent job ! Thanks a LOT !!!

But I got a problem with SetDevicePath.exe

I'm working on my multi boot DVD and Win2000 SP4 (slipstreamed from SP2 to SP4)
When I test my DVD, windows doesen't find any driver in my driver folder. I used setup_dbg.exe to test presetup.cmd.

Everything works well, but before the system reboot, I open a new commandline interpreter to use REG.EXE and to read the registry value

HKLM\Software\microsoft\windows\currentversion\DriverPath

However the returned value is %SystemRoot%\inf

I then launch manually SetDevicePath.exe and re-read the registry tu check the change.

REG.EXE returns the same string : %SystemRoot%\inf

I tried to execute SetDevicePath.exe on a fully installed windows 2000 and used regedit to check the change.

I get the same behavior.

I know that your file is win 2000 compatible because it worked.

I switched my project into multiboot with CD Shell because your executable failed during my last tests. So I restarted from scratch my DVD and implemented cd shell.

Have someone observed the same thing ? Did I forgot a step ??



Here is my essential DVD structure

\
  SETUP
    2K
      PRO
       I386
  DRIVERS
    2K
      <many subfolders>
  2PRO
    SYSTEM32

Now my Presetup.cmd

REM +=======================================================+
REM | Comment out what you don't need. These are mostly     |
REM | examples to give you an idea of how it all works.     |
REM +=======================================================+
SET DRIVERPATH=DRIVERS\2K


REM +=======================================================+
REM | Finding CDROM driveletter                             |
REM |-------------------------------------------------------|
set tagfile=\CDROM_NT.5
for %%i in (c d e f g h i j k l m n o p q r s t u v w x y z) do if exist "%%i:%tagfile%" set CDDRIVE=%%i:
REM +=======================================================+



REM +=======================================================+
REM | We should be already in system32, this is just to be  |
REM | sure                                                  |
REM |-------------------------------------------------------|
%SystemDrive%
cd %SystemRoot%\system32
REM +=======================================================+



REM +=======================================================+
REM | Trick Windows into identifying the original setup.exe |
REM | deleting the setup.exe will not work, just rename it  |
REM |-------------------------------------------------------|
if exist setup.exe ren setup.exe setupold.exe
if exist setupORG.exe ren setupORG.exe setup.exe
REM +=======================================================+



%CDDRIVE%\%DRIVERPATH%\SetDevicePath.exe %CDDRIVE%\%DRIVERPATH%
start %CDDRIVE%\%DRIVERPATH%\WatchDriverSigningPolicy.exe

REM I want to check that windows runs as I and Pyron want ! 
cmd

REM +=======================================================+
REM | Finally start the installation with the originally    |
REM | given parameters                                      |
REM |-------------------------------------------------------|
start /WAIT setup.exe %*
REM +=======================================================+
  

EDIT : I'm wondering if setdevicepath.exe fails since I burned my work on a DVD

This post has been edited by Necros: 17 August 2005 - 09:11 AM

[The Glimmerman]

@Pyron

You stated in the first post that we need to reset the appropriate keys after using WatchDriverSigningPolicy.exe.
I think its not the HKCU, but it should be HKU. Am I right or wrong?

[HKEY_USERS\.Default\Software\Microsoft\Driver Signing]
"Policy"=dword:00000001

[HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\Driver Signing]
"Policy"=hex:01

[HKEY_USERS\.Default\Software\Policies\Microsoft\Windows NT\Driver Signing]
"BehaviorOnFailedVerify"=dword:00000001

[Oleg_II]

Pyron's method works great for me. But when I tryed using SVCPACK folder it seems running svcpack.inf is broken: if an .exe or .cmd file is placed in folder and in svcpack.inf it runs, but when I add Pyron's files, .exe and .cmd files don't run from svcpack.inf. Anybody experienced this behaviour?
Best regards,
Oleg 2

[Bilou_Gateux]

@Oleg_II, TheGlimmerman, Necros, Ixel
Try Drivers From CD (AutoIt Method), A newer, better way. =)

and you can get help from the author: hp38guser.

This post has been edited by Bilou_Gateux: 01 September 2005 - 07:28 AM

[jingder]

*Problem recognized* Driver conflic !!!

This post has been edited by jingder: 07 October 2005 - 08:22 PM

[RBCC]

I am missing somthing:
Where does this line go:
%CDDRIVE%\OEM\bin\SetDevicePath.exe %CDDRIVE%\OEM\drivers?
Could someone please enlighten me? I read through it and followed all the steps, and couldn't find it anywhere!

John

[Bâshrat the Sneaky]

RBCC, on Oct 26 2005, 05:52 AM, said:

I am missing somthing:
Where does this line go:
%CDDRIVE%\OEM\bin\SetDevicePath.exe %CDDRIVE%\OEM\drivers?
Could someone please enlighten me? I read through it and followed all the steps, and couldn't find it anywhere!

John

Try this article.

[Björn_2]

Hi,

has anybody an idea to install the monitor driver silent?
My problem is, that sometimes a window appear which ask me to install the monitor driver.
This window appears in the t-39 (driverinstallation).

Thx.

Björn

[RBCC]

On my CD I have the following directories for my drivers:

I:\xpcd\$OEM$\$1\drivers
|
|---00-av
|
|---01-chip






what do I put here?
%CDDRIVE%\OEM\bin\SetDevicePath.exe %SystemDrive%\drivers

John

[RaynotRoy]

is it possible to put setupORG.exe and presetup.cmd into the $OEM$\$$\SYSTEM32 directory? it sounds easier than adding entries in txtsetup.sif

[zzzz]

RBCC, on Dec 24 2005, 04:57 PM, said:

On my CD I have the following directories for my drivers:

I:\xpcd\$OEM$\$1\drivers
|
|---00-av
|
|---01-chip






what do I put here?
%CDDRIVE%\OEM\bin\SetDevicePath.exe %SystemDrive%\drivers

John

Why do you need this method if you copy the drivers directory to your hard-drive?
And that line you posted is inside the presetup.cmd is it? you don't really know this method.

[Björn_2]

Hi,

I have a problem during an installation of a hp d230m

During the hardware setup in gui setup a blue screen appears with an error message, that there is a problem with the portcls.sys.

There is no way to install this computer with the driver pack.

I used the sound, graphics, chipset and lan packages in the newest version.

I hope, that anybody can help me.

Thx a lot
Björn


I removed the sound pack and the blue screen does not appear. But I don't want to solve the problem in this way.

This post has been edited by Björn_2: 07 January 2006 - 11:57 AM

[5eraph]

Björn_2, update DriverPacks_BASE to v6.01. The problem has just been fixed.

This post has been edited by 5eraph: 09 January 2006 - 04:17 PM

[Björn_2]

5eraph, on Jan 9 2006, 11:15 PM, said:

Björn_2, update DriverPacks_BASE to v6.01. The problem has just been fixed.

I used DriverPacks_BASE v6.01 but the problem exists anymore. I tried to integrate the KB888111 Hotfix myself with the KB888111.exe /integrate: method and the integrate-method of base 6.01. But nothing work.

I think, that there is a wrong driver windows tried to install. Is it possible to get out which driver will be installed during T-35?

Thx
Björn