Search options (Page 38 of 99)

BEAT 1
M1, no QSC, TXT only. fixed

Beat 2.
M1, QSC OFF, chips only. no issue

Beat 3.
M2. QSC OFF, chip, Roe. (only chips)
OK (horay)

beat 4.
M1 on beat 3, QSC OFF, Chip/TXTmode only
CleanUp was OK: Mass not in $Oem$
OK

fifteen variations after that.
four of them tested live in TXT mode in a Live DVD Boot.
all OK (aborted setup when I got asked what partition..)

I cannot test proxy.

I did not yet test M2 repair setup after M2
Somebody gonna have to test that on a LIVE machine he installed with RC2, and I had no free LIVE machine.

Hi abdou,

YOU are the person who can find out.
We maintain a supported device list, and most third party packs have it as well.

YOU can test the current releases, and then find out what it does NOT support.
After that, you can make a REQuest, and you better tell us which driver, and where we get it.

We are not your Sherlock Homes.

Hi
we do not have that driver.
I don't know which model of intel server motherboard this is.
You can provide the model and a link to the driver.

NOTE; If this is urgent, you can integrate the few drivers you need with Nlite.

Thank you,

nous avons un DriverPacks modem.
http://3rdpartydriverpacks.thesneaky.co … 2/?C=M;O=A

topic links
http://forum.driverpacks.net/viewtopic. … 3783#p3783

Hi

we need a product/serial code to get to the XP drivers Sony provide.
(the numbers found under the basrcode sticker.)
http://www.vaio-link.com/os/xp/downgrad … en_GB_cons

You could download them all, and upload or mail them to a driverpacks or main team member, or you could email one of us and provide the code from sticker to one of us, so we can upload the drivers to our FTP.

Hi
it looks like you had QSC off and KDT ON.

DriverPacks is used as last step, do the DriverPacks stream, with qsc ON. (and if you want ktd, ktd ON)

Sorry folks...
Disc based install always was and is main goal.
I think I got carried away when the forum made me think sysprep solutions would work for disc based install.

We can probably tell you how you can see which drivers would stall sysprep.
A LOT of the info is on site, in the packs, in supported device list and in forum.
Making packs ready for Disc based setup with a thirty ton load of drivers is not easy.

I regret to say that we cannot always cater for SYSPREP.
The PE crowd have problems, and the SYSPREP gurus have problems.
We will try to get DriverPacks the perfect solution for DISC based install. We already are the best.

We will try to cater to syprep, and we discussed ideas.
We can tell you how to use DriverPacks, and you should tell us about your issues.
The DriverPacks team cannot have a slogan like 'IT works for Every Thing', because the goals are too different.
But, we can make our slogan, "Help us help you'.

for extra reliability on other chips, please also test disc based install in server 2000/2003

@ chud
I  added the Dell 7400 XP driver to 8015 in section [D1] and did a disc based win 2003 setup, and setup finished.

Now, for sysprep of XP on that type of machine you can remove D2 and L4.
D2 is server only
L4 is an older LSI reference driver for XP, and uses same system file names.

In a disc based setup, the tagname deals with that.

I will have some time available..

chud, was file not found during 2000 or 2003server install?
first thing to try ar remedy is that you disable the skipifOS line. (if present in testpack... I have just started downloading)

YanDhuo wrote a gui to a IRQ (lower level) or PnP (higher level)
Test it for us. Tell us if it truly reports 32 bits zubz.

zhanDhuo  or zhan Dhuo (and lookalikes) have been around for a while.
You can find utilities like this while tracking back to the days of 8 bits.
We want a good sub sys foirmware grabber. (as a yonker says it)
YOU need firmware subsys read at 32 bits or @64 and 32 compatible, not a guessworking txtreader.

You need a firmware reader for a good install.
You need drivers.
Help us make you the best tool.

I can confirm the method 1 D\D issue got eliminated in a IM session "team only" 'interim' test.
SP3 detection works
I hope to run tests on chipset coded folders "interim, team only" soon.

What Jeff did in the last version I recieved in a IM session was a great improvement, and that was a over a week ago. (I was scarce for a while but I had a good many personal excuses.)

What I see right now is that a lot of hard work is done, and nothing gets in the limelight.
Chips? Jeff recieved testfiles so he can test his code and If I know him at all, he will come up with something good for the end user, and will keep the pack developers in mind.

Mass? ditto.

Lan?
The PCI-HWIDS are easy (sorta).. but some of those other lines are mysterious.
What do lines with varying sections of underscores and hyphens do? They fight?