776 Reply by OverFlow

(26 replies, posted in Feedback and Support - DriverPacks Base)

You are welcome to help... However, this has been reported and investigated several times. There are several posts on the forum about it.

Our research leads us to find out there is a limit to the size of a single registry entry. We have come to the conclusion that this is not an issue with DevPath. We believe the issue is exceeding the max size of a single registry entry. If true then this is a limitation of windows XP and not DevPath. It was difficult to find the documentation but as best as i could discover through MS documentation a single registry entry can be no more than 1MB in size. However in practice i believe it is less than that.

while working on a Auto-it script i discovered that it has a limit for the max size of an array and was able to create a workaround by using multiple arrays. This was discovered while i was working on the script to parse the HWIDs contained in a packs INF files (the output is used to populate the supported devices list on our download pages). It may be that DevPath has a similar issue but we don't have the original code for DevPath it was donated to us. I believe it was written in VB. IDK if VB has a similar issue.


If you have time and can figure something out let us know... I would love to fix it.

Go to forum: Feedback and Support - DriverPacks Base

777 Reply by OverFlow

(3 replies, posted in Feedback and Support - DriverPacks Base)

use M2... that is why we created it big_smile

Go to forum: Feedback and Support - DriverPacks Base

778 Reply by OverFlow

(14 replies, posted in 3rd Party DriverPacks)

I did not realize that DriverPacks Finisher was not pulling HWIDs from USB... Hmmm i could look into that if that is true

Go to forum: 3rd Party DriverPacks

779 Reply by OverFlow

(13 replies, posted in Windows 7 Discussion)

I am not thinking that is true helmi... I read that Mac OSX was written on a PC and ported to the MAC, which is why it actually runs better on a PC thana MAC.

I have not personally installed MAC os10 myself but that was what i read... So if it was written on a PC it should install on a PC big_smile.

Go to forum: Windows 7 Discussion

780 Reply by OverFlow

(32 replies, posted in DriverPack Mass Storage)

Thanks CDOB.
Now that you have told me how I will.
Once again you have saved me a mountain of grief trying to figure out how to pull that off in BartPE....

Without you and Hilander... these plugins would still not be done!

I'll get that in the next release... which will be soon.

Jeff

Go to forum: DriverPack Mass Storage

781 Reply by OverFlow

(30 replies, posted in DriverPack Graphics)

it's detaled in the FAQ section of course... tongue

Go to forum: DriverPack Graphics

782 Reply by OverFlow

(5 replies, posted in Other)

We have every confidence that if you follow our tutorial (short version: Nlite first, DriverPacks last). then it will all work flawlessly.

Try it first then report if you have issues.

Best of luck and welcome to DriverPacks

Go to forum: Other

783 Reply by OverFlow

(2 replies, posted in Feedback and Support - DriverPacks Base)

Third party...

Except LAN RIS it's a special case Don't use that without consulting us about your specific need.

Go to forum: Feedback and Support - DriverPacks Base

784 Reply by OverFlow

(101 replies, posted in Feature Requests)

And there you have it Meow. It's already supported, and there is an app to install them.

Solved!

Thanks BadPointer!
Yeah that makes sense... many drivers that we include are 64bit compatable... this is very obvious if you look at the details on the download pages... The thing of it is, Meow doesn't want us to help nor to help us ... he's just a troll big_smile. We don't take the time to help that type... It's OK if you want to though big_smile.

Go to forum: Feature Requests

785 Reply by OverFlow

(12 replies, posted in Translations Team)

you tell me... run base select your language (polish) is there any missing?

Go to forum: Translations Team

786 Reply by OverFlow

(16 replies, posted in DriverPack Mass Storage)

I could turn that book into a volume set... Hearing you loud and clear!

My advice would be to stock up on some replacement parts now... tongue.

Jeff

Go to forum: DriverPack Mass Storage

787 Reply by OverFlow

(32 replies, posted in DriverPack Mass Storage)

Good question... Here's a good answer.

The compressed files have to be renamed so they can coexist in the i386 folder and when they are cached to RAM. They are only extracted when needed. Many drivers will fail if they are renamed. (Actually renamed) so the files INSIDE the cab files keep thier original names. This keeps most or all of them from crashing when used. The possability exists that a maichine MIGHT have two controlers that require two different drivers that both contained a same named file... As far as i know this has never happened. It could... But the odds are millions to one.

Recap It does not matter waht we name the "wrapper" / archive / *.sy_ File... BUT most of the time renameing the contents of the archive / original file will cause failure. Safest thing to do is to NOT rename the original file in the archive.  (i belive this is a some kind of a result of the driver calling itself)

HAGD!

Jeff

Go to forum: DriverPack Mass Storage

788 Reply by OverFlow

(29 replies, posted in Feedback and Support - DriverPacks Base)

Really, really nice to see your posts B.T.S.!  I miss them a lot!

Go to forum: Feedback and Support - DriverPacks Base

789 Reply by OverFlow

(101 replies, posted in Feature Requests)

Again!!!!

Got to give the little kid some props for persistence! tongue

Get those packs pumped out... Shouldn't take too long since there are only about ten drivers, and we'll figure something out for ya.

If you do a first class job of putting the packs together THEN we MIGHT try to help YOU to make SAD / dpinst.exe work


AKA - Put-up or Shut-up

Go to forum: Feature Requests

790 Reply by OverFlow

(32 replies, posted in DriverPack Mass Storage)

That's how things get done around here...
It's all about the teamwork!
As individuals this could never be done... As a community / team we contine to succeed.

Thanks to you guys for being part of our team

Go to forum: DriverPack Mass Storage

791 Reply by OverFlow

(13 replies, posted in BartPE - UBCD4Win - WinPE)

ms_1_exc_skipIfOS   ="wxp,w2k3"

the above code marks the entire R4 folder to be skipped for windows XP and windows 2k3 

(which means excluded for bartpe since it only supports xp and 2k3)

[R4]
; BartPE Code
ms_count	 	= 1
ms_1_tag 	= "R4_realtek"
ms_1_sysfile 	= "Rtenicxp.sys"

enabled for XP and 2K3 (Fully enabled) for BartPE

=====================

[R4]
; BartPE Code
ms_count	 	= 1
ms_1_tag 	= "R4_realtek"
ms_1_sysfile 	= "Rtenicxp.sys"
ms_1_exc_skipIfOS   ="wxp"

Disabled for XP in BartPE

=========================

[R4]
; BartPE Code
ms_count	 	= 1
ms_1_tag 	= "R4_realtek"
ms_1_sysfile 	= "Rtenicxp.sys"
ms_1_exc_skipIfOS   ="w2k3"

Disabled for Windows 2003 in BartPE

=================================

[R4]
; BartPE Code
ms_count	 	= 1
ms_1_tag 	= "R4_realtek"
ms_1_sysfile 	= "Rtenicxp.sys"
ms_1_exc_skipIfOS   ="wxp,w2k3"

Completely Disabled for BartPE = IIRC the last one is read the same as:

;[R4]
; BartPE Code
;ms_count	 	= 1
;ms_1_tag 	= "R4_realtek"
;ms_1_sysfile 	= "Rtenicxp.sys"
;ms_1_exc_skipIfOS   ="wxp,w2k"

Go to forum: BartPE - UBCD4Win - WinPE

792 Reply by OverFlow

(32 replies, posted in DriverPack Mass Storage)

If those HWIDS are missing from

ms_count=3
ms_1_deviceName="Compaq HP ProLiant SCSI"
ms_1_tag="symc8xx"
ms_1_sysFile="CPQ32FS2.sys"
ms_1_hwids="PCI\VEN_1000&DEV_0001,PCI\VEN_1000&DEV_0003,PCI\VEN_1000&DEV_000a, PCI\VEN_1000&DEV_000b,PCI\VEN_1000&DEV_000c,PCI\VEN_1000&DEV_000f,PCI\VEN_1000&DEV_0012"
ms_1_isBusExtender=false
ms_1_exc_skipIfOS="w2k"
ms_1_exc_replaceIfOS="wxp,w2k3"

Then it is a mistake / BUG ... (MR_smartEpants! HELP!!!)

I had that right when i fixed the bug... They must have gotten dropped (again) diring a subsequent update of DriverPack MassStorage.

GOOD EYE my man!!!! We'll get that fixed!

Normaly we say please "help us to help you"  BUT...
Now i think i have to say "Helping you has helped us!" Thank you.

Jeff tongue

Go to forum: DriverPack Mass Storage

793 Reply by OverFlow

(16 replies, posted in DriverPack Mass Storage)

I doubt that... i expect IDE emulation to disappear... It is already being phased out on many platforms. You don't see MFM and RLL support any more do you?

Probably you will jsut need to be careful when you purchase...
Make sure you buy a MB that has XP SATA drivers available. tongue

I really don't know why you think you will be running XP on hardware 20 years from now or even 8 years from now.

although i must admit i have a DOS 6.22 and win 3.11 box here with a 5 1/4 floppy and a QIC drive in it... BUT it is running on a DFI Socket 7 with a 486 processor.... Just because it won't die. I would also like to point out it is just a conversation piece and something to show off like an old trophy. The point is if you want to run a 20 Year Old OS run it on a ten year old platform.

If it is because you have some softwware you are married to... Then simply run it in a Virtual Machine. OR Windows 7 has a XP compatiblilty mode... whereby the XP kernal is loaded into ram with the Win 7 kernal and that works very nicely.

What is it you hope to achieve?

Go to forum: DriverPack Mass Storage

794 Reply by OverFlow

(16 replies, posted in DriverPack Mass Storage)

it is unlikely that future chipsets drivers will be written to support XP. the current chipset drivers are probably the last of the line. EOL for XP is in two years.

If you slipstream Chipset and Mass you are good to go. Much as our Mass storage drivers are all inclusive so are our Chipset drivers. I can't garauntee that you will not have to update your disc over the next 20 years... But you can't do any better for today.

If you don't install Chipset you may find that you can find and install the HDD and get through textmode and PE stages of setup but will then crash at the third stage of setup, GUI mode. MR smartepants is correct if all you want is mass storage support then you must install the drivers that Mass Storage are dependent on IE Chipset.

You can't put a capstone on a pyramid if you have not built the base first.

Go to forum: DriverPack Mass Storage

795 Reply by OverFlow

(32 replies, posted in DriverPack Mass Storage)

those files are left behind and unchanged (SYMC810.SY_ SYM_HI.SY_) in case DriverPacks is uninstalled...

So yes it is a complete removal... you may notice that all of the old drivers are retained for purposes of uninstallation.
What you see as unfinished is not the case at all, they are left intentionally and deliberately. big_smile This may be confusing if you don't think it through completely LOL wink. I hope i have cleared your possable confusion (no update to BASE is required, it already is processing the files 100% correctly. BASE will throw an error if the files do not get overwritten during uninstall.

On the other hand
Yes the BARTPE section needs an update that i have not had time to implement yet. No bug report has surfaced as a result (yet).

Go to forum: DriverPack Mass Storage

796 Reply by OverFlow

(16 replies, posted in DriverPack Mass Storage)

You stated that you wanted the widest support possable...

In that case you should add all the main packs... big_smile.
Mass, chipset, LAN, WLAN, Grapihcs and Sound.

Go to forum: DriverPack Mass Storage

797 Reply by OverFlow

(32 replies, posted in DriverPack Mass Storage)

if the mass ini contains a blank HWID that driver is REMOVED

IE 

[C]
ms_count=3
ms_1_deviceName="Compaq HP ProLiant SCSI"
ms_1_tag="symc8xx"
ms_1_sysFile="CPQ32FS2.sys"
ms_1_hwids="PCI\VEN_1000&DEV_0001,PCI\VEN_1000&DEV_0003,PCI\VEN_1000&DEV_000a,PCI\VEN_1000&DEV_000b,PCI\VEN_1000&DEV_000c,PCI\VEN_1000&DEV_000f,PCI\VEN_1000&DEV_0012"
ms_1_isBusExtender=false
ms_1_exc_skipIfOS="w2k"
ms_1_exc_replaceIfOS="wxp,w2k3"
ms_2_deviceName="LSI Logic C8100 PCI SCSI Host Adapter"
ms_2_tag="symc810"
ms_2_sysFile="CPQ32FS2.sys"
ms_2_hwids=""
ms_2_isBusExtender=false
ms_2_exc_skipIfOS="w2k"
ms_2_exc_replaceIfOS="wxp,w2k3"
ms_3_deviceName="LSI Logic C896 PCI SCSI Host Adapter"
ms_3_tag="sym_hi"
ms_3_sysFile="CPQ32FS2.sys"
ms_3_hwids=""
ms_3_isBusExtender=false
ms_3_exc_skipIfOS="w2k"
ms_3_exc_replaceIfOS="wxp,w2k3"

"CPQ32FS2.sys" is renamed to  symc8xx (over writing it)
symc810 and sym_hi are removed completely

HOWEVER the HWIDS that symc810 and sym_hi previously supported are now supported by the new CPQ32FS2.sys driver that is now renamed to symc8xx.sy_

so all the HWIDS from all three drivers are now supported by symc8xx (which is actually CPQ32FS2)

I don't mean to be an @$$ but there is no possable way that our team will ever support XP64. It was, and always will be, one if the biggest POS that MS ever came out with ranking right up there with windows ME and Vista...

Sorry No hope at all. (you asked so nicely i really am sorry)
http://forum.driverpacks.net/viewtopic.php?id=2651
Asked and answered a thousand times hmm

Go to forum: DriverPack Mass Storage

798 Reply by OverFlow

(8 replies, posted in BartPE - UBCD4Win - WinPE)

download and test with ubcd4win... compare the two...

I use UBCD4Win with WinSetupFromUSB Works great... no manual steps

Thank you for stopping by and having nice things to say!

Welcome to DriverPacks!

Go to forum: BartPE - UBCD4Win - WinPE

799 Reply by OverFlow

(16 replies, posted in DriverPack Mass Storage)

You can NOT integrate our mass storage drivers with nLite... You must use our app DriverPacks BASE. AFTER you are done using nLite.

See our tutorial linked in our signatures. big_smile

Go to forum: DriverPack Mass Storage

800 Reply by OverFlow

(3 replies, posted in BartPE - UBCD4Win - WinPE)

That would be awesome, Wim will flip.

@everyone: If you can't donate then at least click through on our sponsors banners every little bit helps.

Go to forum: BartPE - UBCD4Win - WinPE