Search options (Page 2 of 213)

You are correct. It fails because the ISO is not mounted ofter the reboot. So files are not found.

Try adding the OEM folder to the root of your thumb and see if that makes it all flow nicely.
Or copy the OEM folder to C:\
- it will need to be deleted later

Welcome to DriverPacks.net

yup hardware is fine, windows broken. Agreed.
I expected re-enumeration to restore it. Ghost drivers show up in safe mode.

Story: (with relevant point)

I am at a customer premise (CP). Printer will not work. Spent two hours dinking with it, like you have. Finally i get annoyed and go and get an identical printer from the other side of the office. I plug it in... it works fine. Plug the non working printer into the slot the borrowed unit came out of... it works fine. swap them back and it no worky again.  I fixed it by SWAPPING them out. The printers are NOT identical to windows, I suppose so you could connect ten of the same model to one print server PC.

Windows had separate driver stack for each of the printers, one was broken, one was fine. The broken driver stack was tied to a SPECIFIC printer. and to find the fix for the driver for that one certain printer was buried in the registry somewhere? Maybe?  I Swapped the two identical printers out and forgot about it. Why find the needle in the haystack use the other one in the sewing kit .

I would bet big money you have exactly the same issue. Too bad you don't have an identical burner to prove it out.

I am a computer guy from way back like you and have worked for myself for decades.

Time is money, quickest, easiest (cheapest) first.
                         Unless its personal

Jeff

PS I worked in one of the best shops in the city back in the 90s. Never ever used a wrist strap, ever. Also never had an ESD issue. We used to leave them plugged in, grounding the case. If you are touching the case... and the case is grounded what the h*ll do you need a strap for??? Cases should be grounded, not people. Although I do like people who are grounded that is yet another topic. One thing we did do was to water the carpet, with a watering canfor flowers... LOL. We built high end stuff, daily. NEVER had an ESD incident.  One time a test lead fell into a CRT monitor we were repairing and it fried in spectacular fashion, but never static.

PSS If windows did what it was supposed to do I would be out of a job... right?

Good question...

We decided to drop support for XP when Microsoft did. There is not the demand for XP there once was. We used to get 3 million downloads in two days, now we get half a million a year. That is just the demand side. On the supply side we used to have ten people working on the packs, now we have none. We used to have a testing team too...

Yup if you have ten year old PC's and ten year old software then XP makes sense. However you stated that you had new Motherboard's. That being the case you are not going to be able to realize the full potential of the new hardware with XP. Some of the hardware may not work at all (no drivers).

the first sticky in this forum
http://forum.driverpacks.net/viewtopic.php?id=5336

or check these (you will notice one of them is driverpacks solution)
http://forum.driverpacks.net/viewforum.php?id=16

I haven't tried this one but BadPointer has been around a while... and it looks promising.
feedback in that thread would be nice if you do try it.
http://forum.driverpacks.net/viewtopic.php?id=10794

Questions are good, we like that. Search is better, we like that even more.

Welcome to DriverPacks.net

Jeff

WOW... Married I guess you are 28 now... A year older than I was when I got married almost 26 years ago. I wish you both many years of happiness!

Jeff

We would be glad to have help, it's the fuel that runs our engine.

Techdud did a lot of experimental work, and used some unconventional ideas, which is fine. You could start with his packs or you could start with some existing finals and update those. It will probably be more stable and easier to start with finals but that is up to you. SamLab may have some stuff too. He's a member here that releases packs on his own site. At one time he would simply release our nightlies / test packs. The feedback we got from him was great, and since none of us speak Russian it opened an untold number of non English speaking people to the testing team, and enabled us to finalize packs more quickly. What I am getting at is his packs should be updated versions of our DriverPacks from here, and might (or might not) be stable. That also might be a good place to start from for a final.

mr_smartepants and I decided a long time ago that we weren't going to release anymore NT5 packs. It's a lot of work and not a lot of need. BUT a lot of time has gone by since they were updated and released. Once in a while I think it's still worth doing.  If you put in the work to assemble them and submit nightlies (beta) and Release Candidates (RC) then I'll final test and release them as finals.   

I have added you to the testing team and you will find some new forums are now exposed to you.

Welcome to the DriverPacks team

Jeff

Sorry i missed this post previously

Wow, IDK...

If anybody could crack that nut it would be CDOB. The better option would a be newer version of PE. (PE3, PE4, or PE5)

If your PE supports the drivers it makes life a lot easier.

try 911cd or winbuilder or msfn - if cdob doesn't pop in here soon

Welcome to DriverPacks.net

sorry it took so long to respond

you can update / downgrade - - - IF you have made no changes after you added the DriverPacks.

those three files and some others are RESTORED when you do the following

MAKE A COPY.

ON THE COPY run DriverPacks BASE select none of the packs and hit slipstream. the DriverPacks are now removed and .org files restored.

Run BASE again with desired DriverPacks.

NOTE: it is only necessary to run BASE if you want to change Mass Storage Text Mode all the other packs can be simply swapped out. ;P

Jeff

I don't understand the question...

can you be more specific?

Not enough details to give a good answer.

1) That file might be corrupt on your image. try a different media / install source.

2) That machine may have a hardware or settings error.
    remove and re-seat all cards and ram and cables.
    dust / clean all fans and vents and heat sinks.
    Reset BIOS settings to factory particularly memory timings and select IDE instead of ATPI setting.

3) (you checked already) HDD bad sectors.

Welcome (back) to DriverPacks.net

It is supposed to read "Where did you get that?" the text  is cut off...

Wow you are the first one to find a bug in my code in six years. You get the extremely rare opportunity to report that over at the bugtracker!

What that means is you have a version that is NEWER than our latest official release. Which begs the question, where did you get a version newer than our latest??? Our testing team members would see this all the time. Wim wrote that in the original code and I never changed it, most of us think it is just too funny !

Welcome to DriverPacks.net and thanks for reporting!

Jeff

PS Moved to "Feedback and Support" forum from the "feature requests" forum.