• Registered: 2006-05-30
  • Posts: 81

Topic: [Existing Feature] [REQ] 8.3 naming for DP's

I'd like to see DP Base auto-rename DP's to the 8.3 naming convention automatically into the OEM folder.

During testing of Packs, or if sound, cpu, graphics gets beyond version 9, the install doesn't work, you get file not present when DriverPacks finisher tries moving the flies at end of installation.  This occurs becaus they have DPSAymmvv.7z, DPSBymmvv.7z, DPCPymmvv.7z, DPGAymmvv.7z, DPGBymmvv.7z and DPGCymmvv.7z... all of which become 9.3 (or more if testing nightlies) in the event exceeding 9 on the version, which fails during the DOS mode copying.  If DP Base auto-renamed them this issue would be resolved.... I'd suggest leaving the version out completely or leaving DP off of the file names and still auto 8.3 correction.  Could even make a DP folder inside OEM folder if you wanted ppl to be able to know they are the DP's.  The last method would need changes to the presetup.cmd file obviously.

Anyway, just some thoughts running around my head here..... thanks for entertaining me smile

always remember.....
YCGIYWG (You Can't Get, If You Won't Give)
DizzyDen
  • Helmi
  • Moderator & Translator (German)
  • Offline
  • From: Germany
  • Registered: 2006-05-27
  • Posts: 1,799

Re: [Existing Feature] [REQ] 8.3 naming for DP's

I'm not sure I understand you correctly.

What settings are you using and where does this "file not found" error appear?

I am using M2 and all the DriverPacks (officials and 3rd party DriverPack, alongside with many nightlies) which is definately beyond the count of 9 and I cannot find any "file not found" entries in my DPsFnshr.log.

Besides, the 7ZIPped files in my OEM folder on the source all have 8.3 convention names so I don't even see where you problem could stem from.

http://d1syubgj0w3cyv.cloudfront.net/cdn/farfuture/AeXmpESLemRyQ4RE-dgdjRhN_hKaXMe7woWjOK2wsnk/perpetual:forever/userbar/moderator-3.png

Coming up next - useful links:
• If you like this project, please support it with your donation!      • Grab your HW info (HWIDs) here!     
• If you are a newbie, be sure to check out the DriverPacks tutorial!     • Here's how to create your own DP!
  • From: Cambridgeshire, UK
  • Registered: 2007-01-27
  • Posts: 6,226

Re: [Existing Feature] [REQ] 8.3 naming for DP's

I agree with Helmi.  In each and every integration I've done, the DP Base has always renamed the DriverPacks into the OEM folder in the 8.3 format.
I never use method 1 though, but I doubt that would be any different.

Read BEFORE you post.  HWID tool   DriverPacks Tutorial   DONATE!
http://driverpacks.net/userbar/admin-1.png
Not all heroes wear capes, some wear Kevlar!
  • Registered: 2006-05-30
  • Posts: 81

Re: [Existing Feature] [REQ] 8.3 naming for DP's

To alleviate any confusion, everything apears to copy correctly.... APPEARS TO.... but, that is because during initial copying, it is merely extracting *.7z to %SystemDrive%\D.... following reboot, everything appears to install correctly.... following next reboot... when DPSFINISHER begins, you will get cannot move \D\WHATEVER\DRIVER the file does not exist....

Researching, I discovered I have 7z files with very long filenames (did not rename some nightlies, etc....)  hence, I suspect the reason for failure is in extracting files with longer than 8.3 during text mode.... figured forcing to 8.3 by DPbase may avoid the issue.  This is what made me think of situations where you COULD have (as an example) DPSA81210.7z.... not that it has happened, but could be avoided by having DPBase FORCE 8.3 names.

BTW, I always use M2, slipstream all DP's (no 3rd party, but a lot of testing of nightlies and my own modifications to them) KTD for all slipstreamed DP's, I do set the KTD folder to %SystemRoot%\System32\Drivers (so they will be in with all other drivers, only in their folder structure) and (not that it matters for this particular issue) QSC enabled.

Here is PART of the DPSFinisher log file (all errors correspond to DP's with long filenames in OEM folder)

2008-02-18 13:41:42 : <ERR>  Could not apply KTD on "C:\D\CP", since it does not exist!
2008-02-18 13:41:47 : <ERR>  Could not apply KTD on "C:\D\G\A\1", since it does not exist!
2008-02-18 13:41:52 : <ERR>  Could not apply KTD on "C:\D\G\A\2", since it does not exist!
2008-02-18 13:41:57 : <ERR>  Could not apply KTD on "C:\D\G\N\1", since it does not exist!
2008-02-18 13:42:02 : <ERR>  Could not apply KTD on "C:\D\G\N\2", since it does not exist!
2008-02-18 13:42:07 : <ERR>  Could not apply KTD on "C:\D\G\N\6", since it does not exist!
2008-02-18 13:42:12 : <ERR>  Could not apply KTD on "C:\D\G\3", since it does not exist!
2008-02-18 13:42:17 : <ERR>  Could not apply KTD on "C:\D\G\A\4", since it does not exist!
2008-02-18 13:42:22 : <ERR>  Could not apply KTD on "C:\D\G\A\5", since it does not exist!
2008-02-18 13:42:27 : <ERR>  Could not apply KTD on "C:\D\G\AS", since it does not exist!
2008-02-18 13:42:32 : <ERR>  Could not apply KTD on "C:\D\G\I", since it does not exist!
2008-02-18 13:42:33 : <ERR>  Could not apply KTD on "C:\D\G\N\3", since it does not exist!
2008-02-18 13:42:34 : <ERR>  Could not apply KTD on "C:\D\G\N\4", since it does not exist!
2008-02-18 13:42:34 : <ERR>  Could not apply KTD on "C:\D\G\N\5", since it does not exist!
2008-02-18 13:42:35 : <ERR>  Could not apply KTD on "C:\D\G\M", since it does not exist!
2008-02-18 13:42:36 : <KTD>  Moved drivers inside "C:\D\G\S" to "C:\WINDOWS\System32\Drivers\D\G".
2008-02-18 13:42:36 : <KTD>  Moved drivers inside "C:\D\G\S3" to "C:\WINDOWS\System32\Drivers\D\G".
2008-02-18 13:42:36 : <KTD>  Moved drivers inside "C:\D\G\T" to "C:\WINDOWS\System32\Drivers\D\G".
2008-02-18 13:42:36 : <KTD>  Moved drivers inside "C:\D\G\V" to "C:\WINDOWS\System32\Drivers\D\G".
2008-02-18 13:42:36 : <KTD>  Moved drivers inside "C:\D\G\X" to "C:\WINDOWS\System32\Drivers\D\G".
2008-02-18 13:42:36 : <ERR>  Could not apply KTD on "C:\D\G\A\3", since it does not exist!
2008-02-18 13:42:37 : <ERR>  Could not apply KTD on "C:\D\G\N\3", since it does not exist!
2008-02-18 13:42:37 : <ERR>  Could not apply KTD on "C:\D\G\N\4", since it does not exist!
2008-02-18 13:42:38 : <ERR>  Could not apply KTD on "C:\D\L", since it does not exist!
2008-02-18 13:42:41 : <KTD>  Moved drivers inside "C:\D\M" to "C:\WINDOWS\System32\Drivers\D".
2008-02-18 13:42:41 : <ERR>  Could not apply KTD on "C:\D\S\CR\1", since it does not exist!
2008-02-18 13:42:42 : <ERR>  Could not apply KTD on "C:\D\S\CR\2", since it does not exist!
2008-02-18 13:42:42 : <ERR>  Could not apply KTD on "C:\D\S\CR\3", since it does not exist!
2008-02-18 13:42:43 : <ERR>  Could not apply KTD on "C:\D\S\N", since it does not exist!
2008-02-18 13:42:43 : <ERR>  Could not apply KTD on "C:\D\S\R", since it does not exist!
2008-02-18 13:42:44 : <ERR>  Could not apply KTD on "C:\D\S\V", since it does not exist!
2008-02-18 13:42:44 : <ERR>  Could not apply KTD on "C:\D\S\A", since it does not exist!
2008-02-18 13:42:45 : <ERR>  Could not apply KTD on "C:\D\S\AV", since it does not exist!
2008-02-18 13:42:45 : <ERR>  Could not apply KTD on "C:\D\S\C", since it does not exist!
2008-02-18 13:42:46 : <ERR>  Could not apply KTD on "C:\D\S\CI", since it does not exist!
2008-02-18 13:42:46 : <ERR>  Could not apply KTD on "C:\D\S\CO", since it does not exist!
2008-02-18 13:42:46 : <ERR>  Could not apply KTD on "C:\D\S\CR\4", since it does not exist!
2008-02-18 13:42:47 : <ERR>  Could not apply KTD on "C:\D\S\CR\5", since it does not exist!
2008-02-18 13:42:47 : <ERR>  Could not apply KTD on "C:\D\S\CR\6", since it does not exist!
2008-02-18 13:42:47 : <ERR>  Could not apply KTD on "C:\D\S\E", since it does not exist!
2008-02-18 13:42:47 : <ERR>  Could not apply KTD on "C:\D\S\H", since it does not exist!
2008-02-18 13:42:47 : <ERR>  Could not apply KTD on "C:\D\S\M", since it does not exist!
2008-02-18 13:42:48 : <ERR>  Could not apply KTD on "C:\D\S\S", since it does not exist!
2008-02-18 13:42:49 : <ERR>  Could not apply KTD on "C:\D\S\SC", since it does not exist!
2008-02-18 13:42:49 : <ERR>  Could not apply KTD on "C:\D\S\SI", since it does not exist!
2008-02-18 13:42:50 : <ERR>  Could not apply KTD on "C:\D\S\SM", since it does not exist!
2008-02-18 13:42:50 : <ERR>  Could not apply KTD on "C:\D\S\T", since it does not exist!
2008-02-18 13:42:50 : <ERR>  Could not apply KTD on "C:\D\S\TR", since it does not exist!
2008-02-18 13:42:50 : <ERR>  Could not apply KTD on "C:\D\S\Y", since it does not exist!
2008-02-18 13:42:50 : <ERR>  Could not apply KTD on "C:\D\W", since it does not exist!

Last edited by DizzyDen (2008-02-20 08:08:19)

always remember.....
YCGIYWG (You Can't Get, If You Won't Give)
DizzyDen
  • From: Cambridgeshire, UK
  • Registered: 2007-01-27
  • Posts: 6,226

Re: [Existing Feature] [REQ] 8.3 naming for DP's

You mention the G_A DP (which I have a copy of on my desktop) and in the entire DP there is only a single file that's not 8.3 compliant in the A1/B_58538 directory.
amdpcom32.dll

There are no non-8.3 compliant files in N1.

Are you renaming the DriverPacks in any way(before/after integration)?

During integration, DPBase automatically renames the DriverPacks for 8.3 compliance and even places a .txt file in the OEM folder telling you which DriverPacks were renamed and to what.
Besides, 8.3 filenames are only a concern during textmode setup.  Once setup is complete and the finisher runs at either GUIrunonce or ROE, long-filename support is enabled anyway.

Anyway, you could have a DP with the filename DP_Graphics_A_wnt5_x86-32_802_nightly_big_hairy_long_file_name_wowthisisreallylong.7z and it'll still get truncated down to DPGA802n.7z during integration by the Base.

Last edited by mr_smartepants (2008-02-20 17:29:51)

Read BEFORE you post.  HWID tool   DriverPacks Tutorial   DONATE!
http://driverpacks.net/userbar/admin-1.png
Not all heroes wear capes, some wear Kevlar!
  • Registered: 2006-05-30
  • Posts: 81

Re: [Existing Feature] [REQ] 8.3 naming for DP's

mr_smartepants wrote:

During integration, DPBase automatically renames the DriverPacks for 8.3 compliance and even places a .txt file in the OEM folder telling you which DriverPacks were renamed and to what.
Besides, 8.3 filenames are only a concern during textmode setup.  Once setup is complete and the finisher runs at either GUIrunonce or ROE, long-filename support is enabled anyway.

I understand and agree that when dpsfinisher kicks off, whether guirunonce from winnt.sif or roe from cmdlines.txt, that lfn support is enabled, but it cannot copy files that were not extracted to begin with, and I suspect long filenames in the extracting phase is the culprit.  Sometimes i do rename, i do a lot of testing/tweaking, which has come in handy getting some driver packs fixed here.

mr_smartepants wrote:

Anyway, you could have a DP with the filename DP_Graphics_A_wnt5_x86-32_802_nightly_big_hairy_long_file_name_wowthisisreallylong.7z and it'll still get truncated down to DPGA802n.7z during integration by the Base.

If that were the case, there would be no reason for this request.... here is the contents of my OEM folder on my cd following execution of DPBase 8.01 RC2.....

ATICCP.INS
BIN
DPC801D.7Z
DPCP71220.7Z
DPGA8012.7Z
DPGB8012.7Z
DPGC801.7Z
DPL8022.7Z
DPM8028.7Z
DPSA8022NIGHTLY.7Z
DPSB8023NIGHTLY.7Z
DPW802_NIGHTLY.7Z

Those files were NOT forced to 8.3 naming...

always remember.....
YCGIYWG (You Can't Get, If You Won't Give)
DizzyDen
  • OverFlow
  • DriverPacks Administrator & BASE Developer
  • Offline
  • From: Cincinnati
  • Registered: 2006-12-02
  • Posts: 6,730

Re: [Existing Feature] [REQ] 8.3 naming for DP's

Which version of base are you useing?

Base does rename to 8.3 internaly and it always has...

perhaps your local copy of base is corrupted

DP BartPE Tutorial   DP_BASE Tutorial   HWID's Tool     Read BEFORE you post    UserBars!
http://driverpacks.net/userbar/admin-1.png
The DriverPacks, the DP_Base program, and Support Forum are FREE!.

OverFlow's Website

  • From: Cambridgeshire, UK
  • Registered: 2007-01-27
  • Posts: 6,226

Re: [Existing Feature] [REQ] 8.3 naming for DP's

speaking of which...what is the most current nightly of Base?
I've been using RC2 for a while now since RC3a had issues for me.

Read BEFORE you post.  HWID tool   DriverPacks Tutorial   DONATE!
http://driverpacks.net/userbar/admin-1.png
Not all heroes wear capes, some wear Kevlar!
  • Helmi
  • Moderator & Translator (German)
  • Offline
  • From: Germany
  • Registered: 2006-05-27
  • Posts: 1,799

Re: [Existing Feature] [REQ] 8.3 naming for DP's

Yeah, I guess it's RC2, I've been using that lately.

There was a beta3 or so on the nightly server for a couple of days/hours but that was completely broken from what I can tell (didn't even start to slipstream) and was taken down quickly.
The previously (to that beta3...) released RC3 also was a no-go.

http://d1syubgj0w3cyv.cloudfront.net/cdn/farfuture/AeXmpESLemRyQ4RE-dgdjRhN_hKaXMe7woWjOK2wsnk/perpetual:forever/userbar/moderator-3.png

Coming up next - useful links:
• If you like this project, please support it with your donation!      • Grab your HW info (HWIDs) here!     
• If you are a newbie, be sure to check out the DriverPacks tutorial!     • Here's how to create your own DP!
  • Registered: 2006-05-30
  • Posts: 81

Re: [Existing Feature] [REQ] 8.3 naming for DP's

OverFlow wrote:

Which version of base are you useing?

Base does rename to 8.3 internaly and it always has...

perhaps your local copy of base is corrupted

As stated in my post regarding the contents of my OEM folder, I am utilizing RC2.... I will dl it again and test to see if perhaps it is a corrupted dl, but I wouldn't think everything except that portion would function correctly..... but to rule out or further investigate it is worth a shot.

OK, I downloaded 8.1 RC2 again, deleted all files and folders except my Driverpacks folder.  Ran RC2 and my OEM folder at my destination folder contains:
ATICCP.ins
bin
DPC801d.7z
DPCP71220.7z
DPGA8012.7z
DPGB8012.7z
DPGC801.7z
DPL8022.7z
DPM8028.7z
DPSA8022nightly.7z
DPSB8023nightly.7z
DPW802_Nightly.7z

It appears to me that the 8.3 naming convention is broken in the release somehow.

Last edited by DizzyDen (2008-02-21 08:15:22)

always remember.....
YCGIYWG (You Can't Get, If You Won't Give)
DizzyDen
  • From: Cambridgeshire, UK
  • Registered: 2007-01-27
  • Posts: 6,226

Re: [Existing Feature] [REQ] 8.3 naming for DP's

Are you running Vista?
I've got almost the same DriverPacks you have but mine are relabeled:
ATICCP.ins
bin
DP_Modem.7z
DP_Modem.txt
DPC801c.7z
DPCP7122.7z
DPCP7122.txt
DPGA8021.7z
DPGA8021.txt
DPGB8012.7z
DPL8021.7z
DPM8021.7z
DPSA8021.7z
DPSB8021.7z
DPSB8021.txt
DPW802_N.7z
DPW802_N.txt

The corresponding txt files just say:

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

Original filename: DPW802_Nightly.7z

Read BEFORE you post.  HWID tool   DriverPacks Tutorial   DONATE!
http://driverpacks.net/userbar/admin-1.png
Not all heroes wear capes, some wear Kevlar!
  • Registered: 2006-05-30
  • Posts: 81

Re: [Existing Feature] [REQ] 8.3 naming for DP's

Nope, running XP Pro SP2 updated

always remember.....
YCGIYWG (You Can't Get, If You Won't Give)
DizzyDen
  • OverFlow
  • DriverPacks Administrator & BASE Developer
  • Offline
  • From: Cincinnati
  • Registered: 2006-12-02
  • Posts: 6,730

Re: [Existing Feature] [REQ] 8.3 naming for DP's

strange...

the beta that was up briefly was a test of the PROXY feature of base which was broken...

it was intended for a single individual to let me know if my fix for the failed "Proxy settings import" code would work.
I got the feeed back that my fix was valid and pulled it.
It was a snapshot of what i was in the middle of working on at the time... (a quick and dirty test)

i lost about 20 hours of work i did on base last week and became sad... or 8.02.RC would be out already.

DP BartPE Tutorial   DP_BASE Tutorial   HWID's Tool     Read BEFORE you post    UserBars!
http://driverpacks.net/userbar/admin-1.png
The DriverPacks, the DP_Base program, and Support Forum are FREE!.

OverFlow's Website

  • Helmi
  • Moderator & Translator (German)
  • Offline
  • From: Germany
  • Registered: 2006-05-27
  • Posts: 1,799

Re: [Existing Feature] [REQ] 8.3 naming for DP's

mr_smartepants wrote:

Are you running Vista?
I've got almost the same DriverPacks you have but mine are relabeled

It's the same for me here.

Example:

DPGA8021.7z
DPGA8021.txt -->

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

Original filename: DPGA80218_nightly.7z

http://d1syubgj0w3cyv.cloudfront.net/cdn/farfuture/AeXmpESLemRyQ4RE-dgdjRhN_hKaXMe7woWjOK2wsnk/perpetual:forever/userbar/moderator-3.png

Coming up next - useful links:
• If you like this project, please support it with your donation!      • Grab your HW info (HWIDs) here!     
• If you are a newbie, be sure to check out the DriverPacks tutorial!     • Here's how to create your own DP!
  • Registered: 2006-05-30
  • Posts: 81

Re: [Existing Feature] [REQ] 8.3 naming for DP's

hmmmmmmmmmmm, guess i'll keep searching why they are not being renamed for me.....

always remember.....
YCGIYWG (You Can't Get, If You Won't Give)
DizzyDen