LLXX

WHAT? MAKE2GB worked perfectly fine with patched 4.10.2222 - either they broke SetFilePointer in 2225 or something else is at fault. I have also recieved reports of correct operation from other members here. MDGx please post system configuration and if at all possible, test on a virgin install.

You should've just used an upload site, e-mail is not good for sending huge files.

Isn't the beta going to be public? If I want Vista I'll just get the beta, from what I've seen it's quite close to final already. Not that I want Vista, maybe if I need it for something though...

You haven't said whether you're writing program for PC, or for embedded systems. It seems more like the latter.

This is M$'s own GUIDGEN: http://www.microsoft.com/downloads/details...39-ADB270833AFC Here's a command-line version: http://webhome.idirect.com/~jhonz/Utilities.HTM There's a whole lot more of these things, just Google "guidgen" and you'll find moar.

The older ones were decent, but the quality really went down for the newer ones...

Do you have the skills necessary to write your own defragger? If not, I don't think your idea is feasible.

Actually, disabling automatic speed negotiation might help, as the two NICs may be getting confused deciding who is going to establish the speed. Also, it's 100 megabit eth., the actual speed is likely to be around 10 megabytes per second.

http://thewarp.org/blog/index.cfm?mode=ent...4A4B16115705CBF Just block it in HOSTS or hex out the string in one of the DLLs (forgot which one) if you don't want M$ knowing whenever you search.

Anything that I want to test without messing up my main OS.

For files over 192Kb, the default behavior is for Windows to create the destination file and then set its size to whatever the size of the source is, then copy the data. That's what I mean by pre-enlargement. I'm not too sure of the consequences of omitting pre-enlargement... a possible theory is that it might result in more fragmentation with multiple copies executing at once as the clusters are allocated as the file is being copied, while with pre-enlargement the clusters are already allocated before the copying begins. ...and no, I'm not going to patch any other language versions, simply because there are too many languages already, I'm surprised English hasn't become universal yet.

If there aren't any restrictions on topic, just go to a software listing site (freeware/shareware) and look there for ideas.

You should've just edited the program instead of taking a chance and messing up your XP install...

O RLY? Then what's that line doing in the batch file the OP posted? (s)he obviously doesn't want the *.wav's to be around afterwards.Basically the OP just wants to rename *.wav.mp3 to *.mp3

Make sure there is sufficient airflow *to* the fan, not just the fan itself. If the case cooling is bad, the components inside will just keep using the same recirculated air and heat up more.

Three DVD burners. Those and one hard drive will fully fill a standard ATX mobo with 2 IDE channels. Nero had an option to use multiple recorders since a long time ago. ...and there is no need to make duplicate threads, even though they are about duplication!

I created a few files with extension '.wav.mp3' and tried my solution ren *.wav.mp3 *. ren *.wav *.mp3and it does indeed work Basically, the first rename strips off the .mp3 on the end so you're left with a bunch of .wav files, then the second command changes the .wav to .mp3 and it's done. The one-line solution should've been for %%i in (*.wav) do lame --preset medium "%%~nI.wav" "%%~nI.mp3"For use in a batch file, since % expands a variable otherwise.

True copy protection is a myth, it's more like a 'copy hindrance'. If you created the CD with a standard CD burner, it can be copied. Even systems that rely on physical differences in the disks (e.g. ProRing et al.) can be defeated easily, so if you're just creating the CD with your CD burner, you are definitely not going to make anything hard to copy. You don't want others to make a copy of your CD, don't give it to them.

If everything was fine with .2222, use the patched .2222. The newer versions are for systems that don't work with the original 2222 version.The version numbers just refer to M$'s original file versions. The 2225 is a patched 2225, etc.

Intel 865PE-based mobo, not an Intel-made one. As far as I know the 875 chipsets are nearly identical to the 865s, but with additional hardware features such as PAT and support for ECC memory.

Same kernel files whether you get them from your own install or from Wengier's DOS 7.1 creator.

The first link is just to download a 'web installer' which then downloads everything else, the second *is* the 'everything else'.

You win for doing it all on one line

'M!nus'... good idea for a name Indeed, the AOL etc. crap are useless and very much obsolete. In the standard 98se distro even if I uncheck 'online services' in custom install it still installs it and I have to manually delete afterwards. Also themes etc. are pure useless IMHO, you can get better skin/theme enhancements if you want.