the reason is that the raid and non raid drivers are not the same but the hwids are often too similar or perhaps they even overlap...

it is a problem that the manufacurers fail to recognize. IE raid and non raid have trouble coexisting.

in order to resolve these types of conflicts we need users to test that have the hardware available.
(this means you wink)

Try the mass storage release candidate and let me know if it is fixed.

Thanks for posting and welcome back to DriverPacks

PS you forgot to mention which OS and SP level wink tongue big_smile

I just assumed xp sp3... (is there anything else...)

3,027

(1 replies, posted in Installation Platforms)

You have not provided enough info for us to be able to help.

please review read before you post in my signature.

we need to know which version of base and the packs that you used.
What OS you were installing and SP level.
your DPs_BASE.log is prefered and will include the above info.
any updates you added to your OS, nLite or RVM ect...

Thank you and welcome to DriverPacks

3,028

(15 replies, posted in Other)

a very kind offer...

we add drivers when they are reported as missing...
since no missing drivers have been reported, then there are no missing drivers wink

we are aware that some drivers do have newer versions out and the team is working on upgradeing them.
that is the hard part, getting them to coexist.

As i said previously there is no sense in compareing thousands of drivers to each other when it is a given that DriverPacks is a complete set of drivers. I say this because we get a million downlloads a month and never get any reports of missing drivers. what more proof do you need?

on a different note we only add drivers from OEM sources...
that being the case a list of links to OEM files would be the thing to have.
not that we don't trust people - it is just good policy to only use files we have downloaded ourselfs from an OEM.

as always, have a great day

its an addon for the rvmintegrator wink

IE
ati control panel
nvidia control panel
RAID managers
Wireless configuration panels
Realtek audio taskbar icon
ect...

Plus some drivers will not install at all if their setup programs don't run.
and they would be called from the finisher...

if you don't "finish" your install it is not 'done'. smile

speaking of being nosey...

why do you wish to rob us of our 2 minutes of glory?

the extractor uses a wrapper for 7zip

the wrapper was written by a friend of maxximums and donated to us.

The screen(s) is (are) a result of the way 7zip works.

You would have to take this up with the 7zip developer.

the integrator or nlite can be used with the rvm packs... your choice,

not everyone uses nLite...

What would they do with the rvm update packs without the integrator... wink tongue

yes to both questions...

For using the search feature, and answering your own questions in a clearly outstanding manner...
I award you the coveted...

-= DriverPacks hero of the day award! =-

well done!

Jeff

PS you can put ANYTHING in the 'Other' forum...
I believe this is a feedback and support question so i will move it to there...

you mean we have not release in 6 months, there have been many nightlies...
unfortunately they do not make it easy for us to release stable packs... that is not our fault.

x64 mass storage must be written into the base executable itself.
making it a decent amount of work...
(20~30 non paid and unappreciated hours?)
(I say this in direct reference your lack of respect for the team in berateing them about mass storage, sound and the remaining packs which they have been working very hard to get finaled)

----

edit: perhaps this was a language issue...
We have not 'released' any packs
We have 'updated' them all... dozens of times.

----

Thanks for your input and all of your personal contributions to DriverPacks.
you are a valued member and your feedback is important.
have a great day

Jeff

You are correct the x64 version of dpinst is good and can be used with the packs

there are a few x64 drivers that are in the packs (because they are bundled with the 32 bit versions)
you may be surprized if you try it...

There has been a lot more activity in this thread than i would have guessed
... keep voteing and we will see this added.

txtsetup.oem is what you get when you extract R194052.EXE to the SCSIAdapters\MyDriver\ folder...

if you disable mass storage plugin and extract the R194052.EXE to the SCSIAdapters\MyDriver\

you should get  SCSIAdapters\MyDriver\txtsetup.oem and some other files

pebuilder should add that driver only, if DriverPacks mass storage is disabled in plugins.

try that and see it it works...

3,037

(41 replies, posted in Universal Imaging)

good eye Echo_Platoon

it made more sense to me to include the inf and sif files in each packs own folder
and it simplifies the base code and a users ability to manualy delete any packs plugin by simply deleteing its folder.

i would like to keep the new layout, but i don't have to... let me know if i can help.

3,038

(55 replies, posted in News)

Base should be a final by then too !

  it does seem like it will be christmas at DriverPacks

3,039

(41 replies, posted in Universal Imaging)

Thanks Galapo!

3,040

(7 replies, posted in DriverPack Sound)

sp3 includes kb888111 - don't add it...

base will detect and add that kb if required wink

3,041

(7 replies, posted in DriverPack Sound)

are we to assume XP sp3?

were there rvm or other updates?
drivers added or removed with nlite or other means?

it would be awesome if you could please link us to the known working dell driver (on thier site)!

Thanks for stopping by and reporting... it makes DriverPacks better for everybody!

have a great eay and welcome aboard!

3,042

(6 replies, posted in Hardware)

I agree we cover just about everything in the packs...

it is rare something is reported as missing...

although i think i am going to have to code the soundbyte of Wile E Coyote going over the cliff triggered by an api call to the free fall sensor... it's a must have wink tongue big_smile

Hey chud!

Thanks for being a dedicated member who is always bringing quality posts and info to DriverPacks.
It is just crazy that i had not done this sooner...

Please note that i have given you testing team access...
Welcome to the team!
There are no minimum requirements or anything... just do what you always have wink

Please try out the mass storage RC version
You will find it in the previously hidden team forum that is now visible to you.
- let us know if we still need to address this.

Again... thanks for all your help over the last two years

jeff

3,044

(6 replies, posted in Hardware)

free fall sensor... hmmm

now your laptop can scream as it is falling.

AAAAaaaaa.... thud, laptop wimpers after detecting impact,  LOL ;P

R194052 was enough info for me brb

this driver is included with DriverPack MassStorage 8.05 in folder D\M\D2\

It is a much older version than is now available here
http://ftp.dell.com/sas-raid/R194052.EXE

however d2 was updated by L9 in the latest nightly 811r1

http://driverpacks.sytes.net/driverpack … 2_811r1.7z

Try building with that pack and let us know... both 805 and 811r1 should support your hardware.

try to not change a bunch of settings from their defaults in ubcd4win wink









@debugger
value = Parameters\PnpInterface,5,REG_DWORD,1 is in OEM file
wink

i noticed that you had made quite a few adjustments to your build.

perhaps you should run with jsut  a stock build (generic / vanilla / unmodified) with DriverPacks.
failing that disable DriverPacks mass storage and add

SCSIAdapters\MyDriver\txtsetup.oem   

the pebuilder is looking for txtsetup.oem and it is looking for the txtsetup.oem that contains

PCI\VEN_1000&DEV_0058&SUBSYS_1F101028
or
PCI\VEN_1000&DEV_0058&CC_0100

if you link to the driver i can be more specific - i may even add it for you wink

obtain the F6 driver from the OEM and use it wink
(i will be crazy enough to assume you have a floppy)
if not then use the f6 driver to fill in the folder as outlined at the ubcd4win forum...

link to the OEM location of the f6 driver here... as it is the one we will look at to add it properly in mass storage.

no matter which of these three you do you will still need one missing ingredient the 'F6' driver (or sometimes called the textmode driver)

nice info... thanks for including your hwids...

you were useing 2k3 as your source ( it says in the other forum ) that is good info to include here too. wink

Looks like JakeLD is already aware of it.
Be sure you subscribed to this topic so you can be aware when it is added.
Hopefully you will be able to test it for us...
so we know we added it correctly.

Jaak sais - help us to help you!

have a great day and thanks for reporting

yeah... what we do is a real disaster. wink

no. why?