[bitmonster]

Pyron, on Sep 11 2004, 02:48 AM, said:

@bitmonster
You are probably using the setup.exe from the front page. Look here for the "new" one. The original tries to run setupORG.exe after presetup.cmd.

THX for the reply.

Yes you are right. It was the wrong setup.exe. I read the hole thread before and at the end as I wanted to start to make my package, I had in mind there are updated files, so I quick-searched the whole thread for attachements and links. But I must have oversight the most important post.

Might be time to update the start-posting (and include the compressing idea). Actually this method is very nice and quite simple to setup, but this long thread introduces more dead ends and faults than it eliminates.

[Pyron]

I am actually in the process of updating it, I am also modifying my setup.exe. I still have to do a bit of testing, if everything goes well, I'll update the original guide tomorrow.

--
Pyron

[idle.newbie]

@evilvoice
wrote myself a dirty WSH .js to generate DDF for makeCAB, after some tests, .cab might be another option to go with Pyron's guide. take BtS MassStorage pack for example, .7z=1720k(-mx9), .cab=1968k(LZX:21), .rar=2870k(Maximum), .cab's compress ratio is not the best, but we don't need any extra program to extract it, built-in %SystemRoot%\system32\EXTRAC32.exe.
i haven't test if EXTRAC32 works at timeline that Pyron's guide goes. could you test that for me , my box crashed . if EXTRAC32 works with Pyron's guide, maybe i'll go with cab.

attached cabIt.js do the makeCAB thing, give it a folder to compress(in cmd window), output .cab in parent directory named folderName.cab.

Attached File(s)

•  cabIt.js (1.61K)
  Number of downloads: 68

[Bâshrat the Sneaky]

idle.newbie, on Sep 12 2004, 09:33 AM, said:

@evilvoice
wrote myself a dirty WSH .js to generate DDF for makeCAB, after some tests, .cab might be another option to go with Pyron's guide. take BtS MassStorage pack for example, .7z=1720k(-mx9), .cab=1968k(LZX:21), .rar=2870k(Maximum), .cab's compress ratio is not the best, but we don't need any extra program to extract it, built-in %SystemRoot%\system32\EXTRAC32.exe.
i haven't test if EXTRAC32 works at timeline that Pyron's guide goes. could you test that for me , my box crashed . if EXTRAC32 works with Pyron's guide, maybe i'll go with cab.

attached cabIt.js do the makeCAB thing, give it a folder to compress(in cmd window), output .cab in parent directory named folderName.cab.

You can also move 7za.exe into your system32 directory, to get built-in-Windows support!

(like this: $OEM$\$$\system32\7za.exe)

EDIT: Check the first post! Pyron has updated the guide!

[serialzs]

@pyron

1st of all thanks for your guide... i make my guide runs great...

Use this code its working and it saves space too...

set tagfile=\WIN51

for %%p 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 "%%p%tagfile%" set CDDRIVE=%%p

Nice New Guide...
THANKS AGAIN...

-=[serialzs]=-

[Pyron]

I already feared that someone would come by someday and say: "Why are you using such an antiquated method to search for the CD?", now it finally happened...
But you are right, it's better and wastes less space, thanks!

--
Pyron

[bitmonster]

I have also a small suggestion to make. Since I like to use more than one compressed-driver-package and also some uncompressed drivers, I have modified my presetup.cmd to something like this:

REM +=======================================================+
REM | Unpack the drivers                                    |
REM +=======================================================+
MKDIR "%SystemDrive%\Drivers"
FOR %%I IN (%CDDRIVE%\$OEM$\Driverz\*.7z) DO "%CDDRIVE%\$OEM$\7za.exe" x "%%I" -y -aoa -o"%SystemDrive%\Drivers"

So it uncompresses every package that can be found in CDROM\$OEM$\DriverZ to HDD\DriverS. Uncompressed drivers I can put into CDROM\$OEM$\$1\DriverS so they will also be copied over to HDD and can be installed through the same call to SetDevicePath.exe.

But this brings me also to another question. Might it be possible to modify SetDevicePath.exe in a way, that it will scan two directories on two different drives? This way one could use compressed and uncompressed drivers simultaneous without the need to copy the uncompressed drivers to HDD and the presetup.cmd would even be more universal.

[Lucius Snow]

Thanks a lot Pyron

I have a few questions about your method, could you please bring me some precisions ?

Quote

4. copy my setup.exe to your I386 directory and overwrite the old one.

You mean your setup.ex_, correct ?

Quote

In case you want to use compressed drivers (and who wouldn't want to ), you have to extract them first, then run SetDevicePath.exe on the newly created directory. Note that you can sort your drivers into as many subdirectories as you like and you can have as many driverpacks as you like, as long as you extract them under a single directory, because SetDevicePath.exe takes only one parameter.

- Extract them where ? Anywhere ?
- Then i run SetDevicePath.exe from inside the folder created by the decompression, right ? But i don't understand what it'll do exactly. Will it update SetDevicePath.exe ? Then i have to put it back in $OEM$\Bin ? Sorry, i'm confused

Quote

Microsoft recommends to reset the DevicePath to "%SystemRoot%\Inf" after setup:

REGEDIT4

[HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\Windows\CurrentVersion]
"DevicePath"=hex(2):25,00,53,00,79,00,73,00,74,00,65,00,6d,00,52,00,6f,00,6f,\
  00,74,00,25,00,5c,00,49,00,6e,00,66,00,00,00

If you used WatchDriverSigningPolicy.exe, you should reset the appropriate keys if you don't want unsigned drivers to be installed without warning:

REGEDIT4

[HKEY_CURRENT_USER\Software\Microsoft\Driver Signing]
"Policy"=dword:00000001

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

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

So that reg must be just added in our existing tweak reg file which applies during runoncex.cmd, that's right ?

One last question :
How will it decompress 7z archives ? Do i just need to add 7za.exe to $OEM$\$$\system32 ?

[Pyron]

Lucius Snow, on Sep 12 2004, 12:30 PM, said:

Quote

4. copy my setup.exe to your I386 directory and overwrite the old one.

You mean your setup.ex_, correct ?

Yes, already corrected.

Lucius Snow, on Sep 12 2004, 12:30 PM, said:

- Extract them where ? Anywhere ?
- Then i run SetDevicePath.exe from inside the folder created by the decompression, right ? But i don't understand what it'll do exactly. Will it update SetDevicePath.exe ? Then i have to put it back in $OEM$\Bin ? Sorry, i'm confused 

You extract your archive into a directory of your choice.
Then you run SetDevicePath.exe <full path to directory of your choice>

Lucius Snow, on Sep 12 2004, 12:30 PM, said:

(snipped regfile)
So that reg must be just added in our existing tweak reg file which applies during runoncex.cmd, that's right ?

Yes.

Lucius Snow, on Sep 12 2004, 12:30 PM, said:

One last question :
How will it decompress 7z archives ? Do i just need to add 7za.exe to $OEM$\$$\system32 ?

Basically, yes. Unless you mean if it extracts your archives automatically, then it's no. You have to do it yourself in presetup.cmd. If you want it to happen automatically, name your archive drivers.7z, place it in \OEM and 7za.exe in \OEM\bin, thats what is already prepared in presetup.cmd. But since you seem to be using the $OEM$ directory structure you better modify presetup.cmd to suit your specific needs.

--
Pyron

[Pyron]

bitmonster, on Sep 12 2004, 11:56 AM, said:

But this brings me also to another question. Might it be possible to modify SetDevicePath.exe in a way, that it will scan two directories on two different drives? This way one could use compressed and uncompressed drivers simultaneous without the need to copy the uncompressed drivers to HDD and the presetup.cmd would even be more universal.

Do you really need this? I don't see any practical use here.
Nevertheless, I think about it.

--
Pyron

[Lucius Snow]

Just tried with VMware and it worked perfectly ! Thank you !

[bitmonster]

Pyron, on Sep 12 2004, 01:08 PM, said:

bitmonster, on Sep 12 2004, 11:56 AM, said:

But this brings me also to another question. Might it be possible to modify SetDevicePath.exe in a way, that it will scan two directories on two different drives? This way one could use compressed and uncompressed drivers simultaneous without the need to copy the uncompressed drivers to HDD and the presetup.cmd would even be more universal.

Do you really need this? I don't see any practical use here.
Nevertheless, I think about it.

As I said, I can work with compressed and uncompressed drivers simultaneous the way it's currently implemented, so I can live with it already. But I think this would make the whole thing even more universal and clever.

And I have the feeling, that there is not much to change in the source of SetDevicePath, so it will support more than one path.

[idle.newbie]

bitmonster said:

compressed and uncompressed drivers simultaneous

in different drive...

that's a good idea, uncompressed for the old way in cd, for testing.

Bâshrat the Sneaky said:

You can also move 7za.exe into your system32 directory, to get built-in-Windows support!

i love that new meaning for built-in.

Pyron said:

I already feared that ...

THANKS A LOT, for your guide & lovely little tools.


and thanks to this forum, somebody always makes me

[evilvoice]

@Pyron, in talking about resetting the devicepath and driver signing, I was looking at presetup.cmd, it seems that devicepath already resets itself to \Inf...is this right, or do I still need the tweak?

@idle.newbie...I will test as soon as I can, but im not quite at the point of testing yet but if you dont test it before I do, I will post my results...Im also there, but itll prolly be like a day or 2. Im sorry

[Pyron]

evilvoice, on Sep 13 2004, 04:36 AM, said:

@Pyron, in talking about resetting the devicepath and driver signing, I was looking at presetup.cmd, it seems that devicepath already resets itself to \Inf...is this right, or do I still need the tweak?

I tried to prepare it in presetup.cmd, that's right. (Actually I didn't test that bit, but I am pretty confident that it works.)

--
Pyron

[evilvoice]

hmmm, im sure this has been adressed, but didnt really see any solutions...INFCACHE.1 exists in every directory on my hard drive, is there a reason for this? setdevicepath is set for %systemdrive%\drivers...so I dont know why its in EVERY folder. Could this have happened because I dont have a drivers folder? I havent gotten to the point to add drivers YET, but I was testing to see if your setup and everything ran, it seemed to...but now this infcache.1 has me worried...I just dont like added files LOL. Also, is anyone else running this and installing hotfixes? My hotfixes no longer seem to install, Im not sure if its because of this or not, but I believe this is the only thing I did differently from the last time I installed.

[Pyron]

Windows adds these in every directory referenced by DevicePath. So when you ran SetDevicePath.exe on a non-existant path, it probably just scanned the whole HD (I should add some error checking...).

--
Pyron

[Thauzar]

This may have been answered previously but, is the 7za.exe we are talking about here the same 7za.exe we used in serialz method? else where can I get it?

For the moment I'll try expanding 7za.ex_ from serialz method...
@pyron when you say it starts the setup of GUI mode, does it count as GUI setup when you nlite a cd to get the classic win2k installation style (no blue kiddish gui during install, only a progress bar).. Anyway I'll find it out soon


And what is this supposed to do? I know it's optional but maybe it's usefull it it's there

REM +=======================================================+
REM | Prepare later installations (optional)                |
REM |-------------------------------------------------------|
REM SET KEY=HKLM\SOFTWARE\Microsoft\Windows\CurrentVersion\RunOnceEx
REM REG ADD %KEY%\998 /V 1 /D "%CDDRIVE%\OEM\bin\t-13_install.cmd" /f
REM REG ADD %KEY%\999 /V 1 /D "REG ADD %KEY%\zzz999 /V 1 /D %CDDRIVE%\OEM\bin\postinstall.cmd /f" /f
REM +=======================================================+

Same thing for this one

REM +=======================================================+
REM | Do other stuff like copying useful tools (optional)   |
REM |-------------------------------------------------------|
REM cd %SystemRoot%\system32
REM %CDDRIVE%\OEM\bin\7za.exe x -y -aoa %CDDRIVE%\OEM\data\System32.7z

Anyway, for my part i'm installing 7zip to the computer so I don't really need to copy 7za.exe to the system32 directory, but what is this system32.7z?


And a last one, cause I'm curious, why is setup.exe run with %1 %2 %3 %4 ?? are those variables? and where do they find their value then?

[Lucius Snow]

@ Thauzar : Yes it's the same 7za.exe. About the two optionals command lines, i don't know what it's for. But i can say i didn't need them for the drivers integration (which seems logical since they're described as "optionnal").

[evilvoice]

@Pyron...I replaced your setup.exe with the original, and my svcpack.inf was run...is there any way to fix it so that it runs when using your setup.exe. im using your current version. But I did narrow it down to when Im running your setup.exe...if svcpack.inf still runs for every one else, could it be dependent on me having a drivers folder? i cant imagine that would be it, but it could be.