Bâshrat the Sneaky

Devcon is a well known CLI tool... Not amazed...

That's as you know MUCH work. I will not start building these unless I'm using BartPE or WinPE on professional basis or unless I'm getting paid for building these. It's just not worth it - for me.

This driver has been included now. Though the new DP Graphics B hasn't been released yet

Thanks for the kind words and welcome to MSFN! Please post the HWID of that ATI Radeon Mobility 9000. Check my signature for a tool.

I know.

No

Read this tutorial. Topic moved to Device Drivers forum. Topic closed.

Eh....? The drivers really are updated...

@Corvettaholic: please post the HWID of that controller. Check my sig for an utility. @mark49: thanks. And the SiWinAcc.sys file is NOT needed for textmode setup.

Nope... If you go that far, you'll have to be prepared to have some patience. This and many more features will be included in the DriverPacks BASE, but not just yet...

First of all: use a DVD, that's alot easier! Secondly, the answers: 1. I suppose you do have TWO cd-rom readers in your pc. If this is the case, you can simply copy the OEM folder to a second CD. This will automatically be handled in the presetup.cmd file! 2. No changes are required.

What hardware config are you installing on?

THAT'S what really interesting If this keyboard would cost 50% less or so, I'd certainly buy it. Now it's overpriced.

This driver has been included now. Though the new DP Graphics B hasn't been released yet

1) Yes. But not without modifying the winnt.sif in case of method 1/3 or without using a fake setup.exe in case of method 2. a.) correct b.) correct c.) correct 2) When using ONLY DP Chipset & M1, only the winnt.sif file will be modified in your I386 folder, but ´more files will be backed-up! Sorry for the very very very late reply!

LOL The update with the following changelog is ready for release: V5.08.1 (13 Aug 05) -Fixed: [DPB]: M1 : winnt.sif: the OemPnPDriversPath would not get written to the winnt.sif file because of an error in the syntax of the Fedit call. -Fixed: [DPB]: M2, KtD: winnt.sif: the Driver Signing Policy disabling entries in the winnt.sif would not get written because of an error in the syntax of the Fedit call. -Fixed: [DPM]: all methods: because of a typo, the wrong nvraid.sys driver would be compressed & copied to the I386 folder. By fixing this, the NVRAID problem might be fixed again. Only... btsunattended.net's server seems to be unreachable... AGAIN... I've had it with this. The contract ends by September 3 and I will NOT sign for another year! This is absolute madness. A solution has been arranged, and I've just contacted PixelHosting's admin to move the domain name. Let's see how long that will take

Oh crap. I'm afraid you're right :'( Luckily most people use method 2... An updated DPs BASE will be online tonight!

Check this topic, in which you've also posted a reply regarding the exact same thing. Topic closed, for obvious reasons

Yes, that is possible, and this has been asked before. Some patience while I'll try to find it please. @sonic: you're banned? :s EDIT: what about this topic?

I've heard www.servermatrix.com has an excellent datacenter. (For you smarties, NO, this is NOT the datacenter for BTSunattended.net )

I'm sorry, probably I've read your problem to fast. Yes, only one or 2 weeks ago I started doing this: because many titles do not describe the issue/question at all. This was not the case for this topic's title, but I need to do that to be able to keep track of things. (note the 'SOLVED' statements in the topic descriptions and the things like 'PROB | ' in front of a topic's title.) Yes of course... a vanilla/SP1 Windows XP CD that has been 'upgraded' with a slipstreamed SP2 also works... Why wouldn't it. (At least it works here... there have been some new issues, but they have been overcome.)

@both: the previous topic has been closed, two topics for the exact same thing is simply silly. I think you can both understand that. @VoYaGeRTM1977: ok this MUST be solved. I have 2 more suggestions: 1) add your REV code, don't change the loading order. 2) change the loading order. 3) add your REV code, DO change the loading order. Please try all 3 of these. If you don't try this, this won't be solved, I'm afraid... @robnjay: OK, now I know why I didn't understand: I hadn't read your last post in the other topic yet. But now I have... Let's get back to the facts: 1) your HWID has been reported before, and the driver to be used with it was the VIAMRAID driver; 2) it didn't work with DP MassStorage's VIAMRAID driver, in your case; 3) it DID work with the VIASRAID driver; 4) it DID work with the VIAMRAID driver you got from MSI. Conclusion: please attach your MSI VIAMRAID driver (i.e. the .inf AND the .sys file)

Discussion will be continued in this topic. Topic closed.

Huh? Very well, then I'll add it: it's onl my todo list now.

Any news?