• Denney
  • DriverPacks newbie
  • Offline
  • From: Brisbane, Australia
  • Registered: 2006-05-27
  • Posts: 11

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

I don't know why but I can't get v6.05 to recognize some of the DriverPacks. I've named the DriverPacks like so:

DP_MassStorage_x86-32_6031.7z
DP_Sound_A_x86-32_603.7z
DP_Sound_B_x86-32_603.7z
DP_WLAN_x86-32_603.7z

I've also renamed my 3rd party DriverPacks to:

DP_HID_x86-32_11.7z
DP_Misc_x86-32_13.7z
DP_Monitor_x86-32_171.7z
DP_VMware_x86-32_11.7z

But none of them are recognized. What do I seem to be missing? The log and INI files are no help:

2006-05-27 21:53:56 : <INIT> Imported settings from settings file.
2006-05-27 21:53:56 : <INIT> Detected DriverPack Chipset 6.05!
2006-05-27 21:53:56 : <INIT> Detected DriverPack CPU 6.03!
2006-05-27 21:53:56 : <INIT> Detected DriverPack Graphics A 6.03!
2006-05-27 21:53:56 : <INIT> Detected DriverPack Graphics B 6.03!
2006-05-27 21:53:56 : <INIT> Detected DriverPack Graphics C 6.03!
2006-05-27 21:53:56 : <INIT> Detected DriverPack LAN 6.03.2!
2006-05-27 21:53:56 : <INIT> Could not detect any 3rd party DriverPacks.
2006-05-27 21:53:56 : <INIT> DriverPacks scanned sucessfully.

So, what should these files actually be named? Other than that, love the new interface and I look forward to the DriverPack updates.

Last edited by Bâshrat the Sneaky (2006-05-31 06:50:26)

Denney's Website

  • Denney
  • DriverPacks newbie
  • Offline
  • From: Brisbane, Australia
  • Registered: 2006-05-27
  • Posts: 11

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

How come you always notice what you've done wrong JUST AFTER you tell the world about it? tongue

Nevermind, I fixed it... I forgot about the wnt5_ bit... :S

Denney's Website

  • From: Denver, CO
  • Registered: 2006-05-27
  • Posts: 96

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

LMAO!

The following sentence is false.
The preceding sentence is true.
  • From: netherlands
  • Registered: 2006-05-27
  • Posts: 57

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

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?

Last edited by muiz (2006-05-28 06:12:53)

http://www.l33tsig.net/sig/1/muiz.png
  • From: Hasselt, Belgium
  • Registered: 2006-05-26
  • Posts: 2,609

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

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 wink

Founder of DriverPacks.net — wimleers.com

Wim Leers's Website

  • From: Denver, CO
  • Registered: 2006-05-27
  • Posts: 96

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

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

The following sentence is false.
The preceding sentence is true.
  • From: netherlands
  • Registered: 2006-05-27
  • Posts: 57

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

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

double work

http://www.l33tsig.net/sig/1/muiz.png
  • From: Hasselt, Belgium
  • Registered: 2006-05-26
  • Posts: 2,609

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

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.

Founder of DriverPacks.net — wimleers.com

Wim Leers's Website

  • From: Denver, CO
  • Registered: 2006-05-27
  • Posts: 96

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

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.

The following sentence is false.
The preceding sentence is true.
  • From: Hasselt, Belgium
  • Registered: 2006-05-26
  • Posts: 2,609

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

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 smile

Founder of DriverPacks.net — wimleers.com

Wim Leers's Website

  • From: netherlands
  • Registered: 2006-05-27
  • Posts: 57

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

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

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

http://img79.imageshack.us/img79/1410/txtsetup0th.th.jpg

http://www.l33tsig.net/sig/1/muiz.png
  • Denney
  • DriverPacks newbie
  • Offline
  • From: Brisbane, Australia
  • Registered: 2006-05-27
  • Posts: 11

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

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

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

Denney's Website

  • From: netherlands
  • Registered: 2006-05-27
  • Posts: 57

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

Ty Denney

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

Last edited by muiz (2006-05-29 00:23:16)

http://www.l33tsig.net/sig/1/muiz.png
  • From: netherlands
  • Registered: 2006-05-27
  • Posts: 57

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

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

Now i get a BSOD

http://img523.imageshack.us/img523/3576/harderror7uz.th.jpg

http://www.l33tsig.net/sig/1/muiz.png
  • From: Hasselt, Belgium
  • Registered: 2006-05-26
  • Posts: 2,609

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

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.

Founder of DriverPacks.net — wimleers.com

Wim Leers's Website

  • From: netherlands
  • Registered: 2006-05-27
  • Posts: 57

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

no i didnt

http://www.l33tsig.net/sig/1/muiz.png
  • Denney
  • DriverPacks newbie
  • Offline
  • From: Brisbane, Australia
  • Registered: 2006-05-27
  • Posts: 11

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

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

Denney's Website

  • From: netherlands
  • Registered: 2006-05-27
  • Posts: 57

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

Ofcourse , i start al my tests with a clean windows

http://www.l33tsig.net/sig/1/muiz.png