[Bâshrat the Sneaky]

No, Win XP doesn't include a 'VMWare driver', VMWare simply emulates a very old piece of PC hardware... And yes, you'll have to test on a real pc

[crazyboot]

Thanks again Bâshrat !
I test it this week-end...and then go bring you info back ;o))

if everything's OK, next stop will be integrating your packs which seem very very complete ;o))

PS : is there a topic or topics about how to expand INF files from differents setup.exe (original driver install packs) ? is there a sure method of extracting all the necessary files for integrating drivers when the setup doesn't support any expand switch ? if not, is there a KB ?
for example, i succedded to extract INF from INTEL CHIPSET setup.exe using -A -S -P swithes, but this didn't worked with INTEL EXTREME GRAPHICS setup.exe

[Bâshrat the Sneaky]

There is. Check the unattended Windows XP guide. Extracting driverfiles is the same as extracting applications

i.e.: any archiving application would be sufficient.

[crazyboot]

Hello again, Bâshrat

Sorry, I didn't understand well. What is "extracting applications" in the offical guide ? Where can I find it ?
And what about "archiving application" ? If you mean like winzip or winrar, I always try them first of all, but very often "open with winrar" is not possible. Or, it is possilbe with the first exe, but then there is still no INF files but only a new setup.exe which cannot be opened by winrar...

See ya'

[Bâshrat the Sneaky]

That was exactly what I meant. But I tend to use 7-zip (freeware).

If it's a InstallShield app (tagfiles: data1.cab, data1.hdr, data2.cab, data2.hdr, etc.), you'll have to use the CLI tool 'i6comp.exe' to extract the files.

If you just have a setup you cannot seem to extract, you have 2 possiblities: 1) it's an Intel drivers setup, if so, please do a search for it; 2) execute the setup but do NOT proceed the installation process. Check the folders 'Downloaded Installations' or 'Temp' or...

[crazyboot]

Hi and ta (thanks again ;o))))

I've made a little search for i6comp.exe and found this interesting how to example ;o)

but my trials with

i6comp.exe e -r data1.cab

and

i6comp.exe x data1.cab

weren't succesfull

EDIT : neither pause nor -v in cmd file made the log stay on the screen, so i don't know why it makes nothing...

[Bâshrat the Sneaky]

The second one should work just fine ... I've used it NUMEROUS times. Are you in the directory where data1.cab is located in?

[crazyboot]

Hello again,

Well the week-end was very nice (beautiful weather ;o))
But, my install of Pyron,'s method didn't made the drivers recognized by my (real) PC
Three yellow "!" for :
- audio driver
- video driver
- modem driver
and all three were in the path...
I ve just installed them manually, after the windows install finished.

My debug of setup windows was well displayed, after the first reboot, and all the lines were OK. It waited a while for SetDevicePath.exe and WatchDriverSigningPolicy.exe jobs, and then made setup continue without any problem.

So, I really don't know how to find where is the problem, and I feel a little far from how to fix it

For the use of i6comp.exe, i tried it on speedtouch driver, and i put the i6comp.exe on system32 directory, and made a little cmd line in the same directory where tdata1.cab was located. But, for this problem I m not too worried, it seems not important to me, compared to the general problem of drivers not recognized during windows xp installation...

See ya'

[scankurban]

Try this...
i6comp x -f data1.cab

[Bâshrat the Sneaky]

Try the setup.ex_ from my DriverPacks BASE then. And are you sure all your paths are right? It seems to me that your drivers didn't get extracted

[crazyboot]

Hello Scankurban, hello Bâshrat

Well, here is a little precision :

My DVD has some boot directories on the root and SETUP with WINXPPRO files.

In \SETUP\WINXPPRO :
- I386
- INSTALL

In INSTALL :
- Drivers
- Applications
and some other specific install directories

And Finally in DRIVERS :
- 001_chipste
- 002_modem
etc. plus SetDevicePath.exe and WatchDriverSigningPolicy.exe, of course

In all subdirectories :
- PC_reference\Name_of_driver\drivers_directories_anf_files

All : audio, modem and video for my trial were well extracted, and it is sure because I've just made them recognized via device manager manually install, after the windows install was finished (i've just manually installed from a directory where, for each, INF files are located on my DVD). So, I don't think the problem lies on extraction, but some other issue ?

Also, i've commented two lines about Drivers in WINNT.INF, so it should be OK too ?

Thank you for your helping and untill next reading.

[zzzz]

I have the following problem: (It happens at the first reboot right after the copying of installation files)



I have WatchDriverSigningPolicy.exe, SetDevicePath.exe and other driver folders in %CDDRIVE%\Drivers\


My presetup.cmd:

set tagfile=\WIN51
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:

%SystemDrive%
cd %SystemRoot%\system32


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


start /WAIT setup.exe %*

[Bâshrat the Sneaky]

Did you delete the WIN51 tagfile at the root of your UWXPCD?


@crazyboot: wow that's some DEEP path! Did you modify the presetup.cmd file to reflect the changes?

[zzzz]

Bâshrat the Sneaky, on May 4 2005, 06:55 AM, said:

Did you delete the WIN51 tagfile at the root of your UWXPCD?

No. My XPCD root source:

[imdos]

well you have updated to sp2 so the file win51 had changed....

if you modify presetup.cmd it will be fixed i geuss

[Bâshrat the Sneaky]

Indeed...

Change

set tagfile=\WIN51

to

set tagfile=\WIN51IP

and it will work

Try to understand what's inside next time!

[zzzz]

Bâshrat the Sneaky, on May 4 2005, 12:47 PM, said:

Indeed...

Change

set tagfile=\WIN51

to

set tagfile=\WIN51IP

and it will work

Try to understand what's inside next time!
<{POST_SNAPBACK}>

Thanks . Pyron didn't explain through this tag file, so I didn't notice .

[Bâshrat the Sneaky]

I edited the first post to make his guide clearer on this point.

[crazyboot]

Hello !!!

Bâshrat the Sneaky, on May 4 2005, 06:55 AM, said:

@crazyboot: wow that's some DEEP path! Did you modify the presetup.cmd file to reflect the changes?
<{POST_SNAPBACK}>

Here is (a part of) my presetup.cmd (very close to Pyron's orginial one) :

...

REM +=======================================================+
REM | Finding CDROM driveletter                             |
REM |-------------------------------------------------------|
set tagfile=\SETUP\CD.txt
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 +=======================================================+

....

%CDDRIVE%\SETUP\WINXPPRO\install\Drivers\SetDevicePath.exe %CDDRIVE%\SETUP\WINXPPRO\install\Drivers
start %CDDRIVE%\SETUP\WINXPPRO\install\Drivers\WatchDriverSigningPolicy.exe

...

This post has been edited by Bâshrat the Sneaky: 05 May 2005 - 02:21 AM

[Bâshrat the Sneaky]

Yes, this should work.

I cleaned up your post, no need to post your entire presetup.cmd