Bâshrat the Sneaky

Ok, but from my understanding, using the method you mentioned above, the after textmode support is done VIA oempnpdrivers path in the winnt.sif. I ONLY want to use pyron's method for After textmode drivers (it allows for easy integration of driver pack update + additions, so I don't have to keep slimstreaming) and plus the drivers remain on DVD. ← Then there's something WRONG with your understanding Method 2 = Pyron's Method != OEMPnPDriversPath in wint.sif *only* Pyron's method *after* textmode setup? It's impossible to use Pyron's method DURING textmode setup, which leaves as only option... after textmode setup. If you still don't understand what it all exactly does, please contact me through MSN...

That never gets old! <{POST_SNAPBACK}> Couldn't agree more

I don't understand why you don't simply slipstream DriverPack MassStorage as it is outlined in the tutorial? Then you have BOTH DURING and AFTER textmode setup, support for MassStorage controllers...

Please post its HWID... maybe your HWID isn't listed yet... though that would be rather exceptional...

So this way, I will get mass storage driver support in textmode? K i will try. ← After reading this... ...I thought you only wanted support AFTER textmode?

Thanks for your attention, Bâshrat the Sneaky. I have saved your little script save_hwid.bat. But I haven't been able to contact my friend since I posted. I left him a SMS but have got no reply yet. Sorry that's not my PC, but a friend's. ← OK, well let me know whenever you get a reply

@ripken204: ...

Omega's driver has more tweak possibilities, which are NOT included in this driver. This is simply a clean ATI Catalyst driver, with just the necessary modifications to get the ATI Mobility Radeon cards to work. This pack is indeed compatible with ALL ATI Mobility Radeon cards, and not just the Mobility X600/X700/X800, like ATI's Mobility Catalyst.

@simpleman: please use the NEW DriverPacks BASE! (V5.07.6) @Chertoianov: hmmm... are you installing onto your 3114r or nForce controller? EDIT: @Siginet: no you're not

My DriverPacks are indeed for Windows XP. But I don't know how this Ghost 9 CD is built, so it might work for you as well. If: -textmode drivers should have entries in txtsetup.sif & dosnet.inf and the .sys files should be placed in the I386 directory; -and PnP drivers should be placed in $OEM$\$1, then it should work fine for you. If you need a guide on how to slipstream mass storage drivers, I'd recommend GreenMachine's guide.

Equal or higher version is recommended. Lower version is NOT recommended (though that should not be a problem, of course).

@avis: SiS180 not working? :s That's new. Please post the HWIDs of both systems, then I can figure out if they're all already supported or not! @Siginet: that work-around has been known for a long time already

So it was a driver issue after all? :s Very strange. Well, the next release is only when nVidia/ATI updates its drivers...

If you'd have looked amongst the stickies... http://www.msfn.org/board/index.php?showtopic=19792 BTW, this methods gives quite often problems, which is why many people DON'T use it. But it may just work fine for your needs.

that means the filename should be in 8.3 format. ← Yes But everything is fixed now!

Eh yes. Easily Just rename 'DriverPack_MassStorage_V*.7z' to for example 'DriverPack_MassStorageAfter_V*.7z' and it will only slipstream the mass storage the drivers the PnP way...

Then what guidance do you need?

Hi there, and welcome to MSFN! The website is still online... please check again.

A save of your original txtsetup.sif HAS been saved: check your I386 folder for the file txtsetup.old As for the rollback: that's possible. Just rename your DriverPacks folder to anything and create a new, EMPTY 'DriverPacks' folder. (We're talking about the DriverPacks BASE here... ) Now complete the slipstream process and everything will be in the state as it was before

BTS DriverPacks BASE V5.07.6 Changelog: V5.07.6 (29 Jul 05) -Fixed: [DPM]: copy_sys_files_to_temp.cmd: obsolete nvcchflt.sys entry were still added. -Fixed: [DPM]: slipstream_DPM.cmd: obsolete nVidia nForce entries were still added. -Fixed: [DPM]: slipstream_DPM.cmd: Silicon Image SiI 3512 SATALink controller may be working again now (work-around attempt). Download Known issues -Bug|non-critical: [DPB] all methods: in winnt.sif: if a section is being updated with new and/or updated entries, it will add a new section if the cases of the sectionname aren't identical. -To-do [DPM]: the Promise misery... making a driver of myself would be the only 'easy' and 'painless' way to solve it.

Interesting! Please mail both your DriverPacks to BashratTheSneaky [at] gmail [dot] com, and I'll try to incorporate your fix. Note that I can only accept 10MB file attachments there, so you'll have to use the 'split archive' option in your compression program. Thanks for reporting back

LOL Please inform yourself better... method 2 IS Pyron's method EDIT: you could have read it in the big tutorial in the uAwiki.

Thanks guys, but KEEP it coming!

You're not keeping the 10.3 rule in mind... The new version is online!