DriverPacks.net Forum - SOLVED: New DriverPack naming (I must be stupid!)

Re: SOLVED: New DriverPack naming (I must be stupid!)

null@example.com (muiz_old) — Mon, 29 May 2006 12:42:37 +0000

Ofcourse , i start al my tests with a clean windows

Re: SOLVED: New DriverPack naming (I must be stupid!)

null@example.com (Denney) — Mon, 29 May 2006 01:32:44 +0000

Have you tried re-creating the ISO image from scratch? $20 says it works then.

Re: SOLVED: New DriverPack naming (I must be stupid!)

null@example.com (muiz_old) — Sun, 28 May 2006 17:53:19 +0000

no i didnt

Re: SOLVED: New DriverPack naming (I must be stupid!)

null@example.com (Wim Leers) — Sun, 28 May 2006 17:45:29 +0000

muiz wrote:

i removed the "=" but that did NOT the trick.
Now i get a BSOD
http://img523.imageshack.us/img523/3576 … 7uz.th.jpg

Eh? That file isn't even touched by the DriverPacks BASE. Probably you edited another line in the txtsetup.sif file without even knowing!

New version will be online within two hours at the most.

Re: SOLVED: New DriverPack naming (I must be stupid!)

null@example.com (muiz_old) — Sun, 28 May 2006 17:42:37 +0000

i removed the "=" but that did NOT the trick.

Now i get a BSOD

Re: SOLVED: New DriverPack naming (I must be stupid!)

null@example.com (muiz_old) — Sun, 28 May 2006 02:59:46 +0000

Ty Denney

This will be fixed in next version? , if so i better wait instead of messing around with my textsetup

Re: SOLVED: New DriverPack naming (I must be stupid!)

null@example.com (Denney) — Sun, 28 May 2006 02:14:29 +0000

Known problem: http://forum.driverpacks.net/viewtopic.php?id=9

Simple fix, remove one of the 2 "=" signs on that line.

Re: SOLVED: New DriverPack naming (I must be stupid!)

null@example.com (muiz_old) — Sat, 27 May 2006 20:25:31 +0000

Thats the way YOU see it , and i am NOT you.

Anyway , after renaming them and slipstream it halted on an error :

Re: SOLVED: New DriverPack naming (I must be stupid!)

null@example.com (Wim Leers) — Sat, 27 May 2006 18:54:51 +0000

razormoon wrote:

There are a lot of programs that I USED to call from guirunonce (I've sinced moved on to runonce).
I noticed that a lot of my app calls weren't doing crap, specifically an important one called VidChngxxxx.exe. After a few months I finally decided to rename that exe and change the reference in winnt.sif to read vidchng.exe and behold. It worked. (8.3 filename)
The reason for the renaming is this...
DPGA603.7z : What the h*ll is this??
DP_Graphics_A_wnt5_x86-32_603.7z : Oh, I see. It's graphics pack A!
Easier to read.

Thanks for clarifying, razormoon

Re: SOLVED: New DriverPack naming (I must be stupid!)

null@example.com (razormoon) — Sat, 27 May 2006 18:51:27 +0000

There are a lot of programs that I USED to call from guirunonce (I've sinced moved on to runonce).
I noticed that a lot of my app calls weren't doing crap, specifically an important one called VidChngxxxx.exe. After a few months I finally decided to rename that exe and change the reference in winnt.sif to read vidchng.exe and behold. It worked. (8.3 filename)

The reason for the renaming is this...

DPGA603.7z : What the h*ll is this??

DP_Graphics_A_wnt5_x86-32_603.7z : Oh, I see. It's graphics pack A!

Easier to read.

Re: SOLVED: New DriverPack naming (I must be stupid!)

null@example.com (Wim Leers) — Sat, 27 May 2006 18:51:09 +0000

muiz wrote:

I rename them , and the base pack is renaming it back......
double work

Nope.

You have to rename to a strict structure, but it's still a long filename. Alot of information is hidden inside them: the name of the DriverPack, for what platform they're designed and its version number. After the slipstream this clearly distinguishable naming system is no longer needed, then we need 8.3 compliancy. So I've made this 'long filenames' especially for you, my users, to make things a bit easier (for the future at least).

FYI: 8.3 compliancy is required for winnt.exe/winnt32.exe initiated installations and I believe some other as well.

Re: SOLVED: New DriverPack naming (I must be stupid!)

null@example.com (muiz_old) — Sat, 27 May 2006 18:45:15 +0000

I rename them , and the base pack is renaming it back......

double work

Re: SOLVED: New DriverPack naming (I must be stupid!)

null@example.com (razormoon) — Sat, 27 May 2006 18:44:21 +0000

I believe they've been renamed for clarity (long filenames). Strictly for clarity.

Re: SOLVED: New DriverPack naming (I must be stupid!)

null@example.com (Wim Leers) — Sat, 27 May 2006 18:44:16 +0000

muiz wrote:

After i renamed them all like this : DP_Graphics_A_wnt5_x86-32_603.7z ( example )
It recognized them , but.......
When i opened the OEM folder i saw that they all where renamed again
so DP_Graphics_A_wnt5_x86-32_603.7z became DPGA603.7z
What is the use of renaming them then?
And the 3th party drivers all have their own .txt file in the OEM folder.
Example : This file had to be renamed to be compatible with 8.3 filenames.
Original filename: DP_VMWare_wnt5_x86-32_v1.1.7z , text file : DP_VMWar.txt : This file had to be renamed to be compatible with 8.3 filenames.

Original filename: DP_VMWare_wnt5_x86-32_v1.1.7z

What is the use of renaming them then?

8.3 naming compliancy

Re: SOLVED: New DriverPack naming (I must be stupid!)

null@example.com (muiz_old) — Sat, 27 May 2006 18:41:47 +0000

After i renamed them all like this : DP_Graphics_A_wnt5_x86-32_603.7z ( example )
It recognized them , but.......
When i opened the OEM folder i saw that they all where renamed again

so DP_Graphics_A_wnt5_x86-32_603.7z became DPGA603.7z

What is the use of renaming them then?

And the 3th party drivers all have their own .txt file in the OEM folder.

Example : This file had to be renamed to be compatible with 8.3 filenames.

Original filename: DP_VMWare_wnt5_x86-32_v1.1.7z , text file : DP_VMWar.txt : This file had to be renamed to be compatible with 8.3 filenames.

Original filename: DP_VMWare_wnt5_x86-32_v1.1.7z

What is the use of renaming them then?