[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.

[Thauzar]

@evilvoice, I don't have any pre-SP3 updates yet on my cd so I really don't know how the setups work with it, but isn't it supposed to start the original setup.exe anyway after presetup.cmd starts? In that case it should not change anything else except seeing and executing presetup.cmd.. well normally...

[evilvoice]

thats what I thought, but its definitely this new setup.exe...Also, if you read, he talks about certain things being out of place, like runonce executing at t-34 or something like that.

[Pyron]

evilvoice, on Sep 14 2004, 07:25 AM, said:

thats what I thought, but its definitely this new setup.exe...Also, if you read, he talks about certain things being out of place, like runonce executing at t-34 or something like that.

RunOnce is indeed running at T-34 but there is nothing wrong with it. If you refer to RunOnceEx, it still runs at T-13.
Try adding keys to RunOnce through HIVESFT.INF, it should be running at T-34.

--
Pyron

[evilvoice]

that was just an example, my problem is when using your setup.exe, svcpack.inf does not work

[Bâshrat the Sneaky]

Thauzar, on Sep 14 2004, 12:20 AM, said:

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 +=======================================================+

This is to add RunOnceEx entries to the registry. You've never heard of RunOnceEx? Then is http://unattended.msfn.org (the guide) the place to be!

Thauzar, on Sep 14 2004, 12:20 AM, said:

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

This is to extract usefull utilities (like pskill, 7za.exe, etc.) directly to the X:\WINfolder\system32 folder. (Does the same as $OEM$\$$\system32, only with (better) extraction!

Thauzar, on Sep 14 2004, 12:20 AM, said:

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?

Those are the parameters to start the REAL setup.exe! Fore more info, you should PM Pyron I think.

[Thauzar]

@Bashrat Nope, never (well I heard of) used runonce or runonceex, a good old batch file is just fine for me, I like that black screen and dos commands, simple and efficient. And it's not the unattended guide that seems to explain more of it in details... looked a LOT easier with batch files.


This troubles me... if svcpack.inf doesn't work, then how will we add the Pre-SP3 hotfixes?

[Thauzar]

This post may be in the wrong thread but: how can I extract compressed drivers from Dell?

I explain: there is a .exe I extract with winRAR that gives me a folder with some setup files, lots of files, and 2 .cab files (i presume the drivers are hidden here). But running the installer extracts the files (where??? not in temp folder ). I am trying to get to the inf to add to my drivers.7z file for my unattended xp but can't get the processor and mouse ones because of that stupid problem. The .cab file doesn't appear to be normal cab files cause I tried expand, and extract and both commands did not recognise the file, expand simply copying the .cab and extract saying wrong file format... winRAR and 7zip neither can uncompress those .cab files...

Thanks

[Pyron]

Well, if it is InstallShield, it doesn't extract itself neccessarily. The installer probably just reads out the cab-files directly. If this is the case, you can only install the drivers and grab them out of your running system with a software like WinDriversBackup(hard to find, pm me if you need it) or My Drivers.

BTW: can someone confirm the svcpack.inf issue? I didn't use it myself for such a long time that I can hardly remember how it works...

--
Pyron

[Thauzar]

@Pyron I'd like to but since there is no updates to add to svcpack.inf yet I can't test it If you know a way I could do a test to help you out PM me and I'll try whatever I can!

[evilvoice]

I will test again, this time without adding the files to my source...and will give any updates...basically, I will be taking an sp2 source, and adding the files to the oem\bin dir and also adding svcpack.inf and my hotfixes, and thats it...maybe something else I am doing is breaking it, but since noone has responded, I figure ill give it another shot.