Bâshrat the Sneaky

You know what? I think I'll try to integrate the 3ware drivers with the regular method anyhow. Then the problems with the txtsetup.oem file will be solved. I've read tens of pages the last two hours, searching for a solution to my problem: 'unexpected error (18), at line 1742'. It seems NOBODY has ever successfully solved this problem with a method, but only by accident. No update today, but tomorrow there will be one!

Now I tested the BASE V5.02.7 and the MassStorage V5.02.1, along with al the others. Guess what? No, it didn't work, but now I got the txtsetup.oem error 18, error on line 1742 again! :@ Anyone with a quick fix? txtsetup.txt

Thanks, Ramona Much appreciated About the loading of 3ware drivers: it's correct and thus it SHOULD! You could compare it at the very beginning of textmode part of setup: there you see all supported controllers being loaded. Well, with this method, it simply loads the 3ware drivers as well!

I've got 3 words for this: WHAT THE F*CK This is DEFINETELY an undocumented method. According to all documentation Microsoft provides us with, you have to use $OEM$\TEXTMODE, I386\$OEM$ and $OEM$\$$\OemDir. Now this is something totally different... But I'm quite convinced that the 'regular version of this method' also works. Nevertheless, it would be very interesting to study the differences. So if you can, please compress it and mail it to me! (if not larger than 0.5 Meg, if larger, please PM me)

huh? It DID work for you when using BASE V5.02?

@snakesnake: ok, then you've got the same error code as several already reported. Thanks! My feeling tells me that we're really close to get everything solved!

Well, I *ONLY* included the 3ware drivers there (which ARE bootable MassStorage devices!). And why not use the regular method for these? Well, that's easy: it simply doesn't work with the regular method! So I use a hybrid method: the txtsetup.oem method for the 3ware controllers, the regular method for all the others. And about secondary MassStorage device drivers: ALL drivers are included there, also the 3ware ones. I hope this reply answers all your questions @zorro1: thanks for the reply. I've got DP MassStorage V5.02.1 here on my HDD, without those drivers. Will test it here, on a REAL LIFE PC, and see if I still get the errors... (fixed some more in the txtsetup.oem part)

Thank you But then it's not related to the txtsetup.sif file, but to the txtsetup.oem method I added. I've indeed found some errors, but I don't know (actually doubt) they could cause this. But you still have a BSOD at the first boot? Please post the error code! Is it a code like STOP: 0x0000007B (some more codes) ?

Nothing seems wrong with it. The problem must lie at my side... Just don't know what. I checked and verified really EVERYTHING, so I have absolutely no clue what *could* be causing this problem...

Thanks RogueSpear. An addition: ALWAYS mention the method you use, and now in particular: mention which DriverPacks BASE you're using!

@Ghostrider & moesasji: which method did you use? EDIT: ok moesasji didn't notice you posted it.

That ATAPI CD error? STILL??? You are using DriverPacks BASE V5.02.6 with the fix in this post in the DriverPacks General Discussion?

Well... IF everything was implemented the way it is automatically done by my DriverPacks BASE, it will be automatically removed. *BUT* because you've changed some things, it will only remove the things that are default. So the things you've added/changed will have to be removed manually...

Found out why it doesn't work properly: But at the same time, in the same text there's a contradiction: But... So I'll remove it! And it also says that it will be included in future Hyperion drivers, so I already know from this moment that I won't include it...

I thought it was possible to check with Devcon if a specific DeviceID was available and if that's true, execute a command. But I cannot find it anywhere? Anyone who can help?

It's impossible that you got this error if you didn't make any changes. Please post EVERY change you made! P.S.: it would definetely be easier if you adapted your things to the method, instead of how you are doing it now...

No double posting please! Topic closed.

WTF... They weren't included in the previous DriverPack MassStorage so I'll release a new version without them! Thanks for your bugreport. Did you also get any BSOD's?

@glent: huh? I'll investigate it... @Ramona: Is this from an installation you COMPLETED and included my DriverPacks? Or are you asking if my DriverPacks 'injected' the 3ware drivers into your current Windows XP setup? @Ghostrider: you're welcome @ixpee: yes you can post here I understand the problem. But I'm quite sure that the .cmd file should be DECOMPRESSED after you've completed my batchfiles.... That's something that's built-in since V5.02.2 or V5.02.3. Are you sure you've used V5.02.6? And you're right about the .exe files that can't be found! Thanks for the bugreport! EDIT: @all: thanks to ixpee I now see that NO control panel is working at the moment when using method 1. Because they are still compressed, they won't work.... Fix tonight...

No, space doesn't matter!

@batman75: I think I've got an even better idea: what if we could /hide/ the download button after you've clicked the ads, and let ONLY appear the actual download link/button?

Papst are the most silent ones. It's not a hype IMO... I thought it was... untill I got 2 of them!

I know someone who's running gameservers, and he uses nothing but Dual Xeons. Dunno if less is also sufficient, I think it depends on what game and how many gameservers you want to run.

Goddammit :@sldfjsmldfjfslmdfj @Ghostrider: that's not the part where it compresses the .sys files to I386\*.sy_ ! It's a bit earlier. Testing it right here as well... it worked like a charm with both methods yesterday! :'( EDIT: no you're right! That IS the problem, but not exactly as you said: the %M% var is overwritten by the method variable, which is ALSO %M%.... Attached a fixed RUN_ME.cmd replace it by the original one in the last step and tell me if it works....

@lilweirddude: lol too late, it's already fixed