Anyone who programs is used to those little gremlins which pop and make things not work, despite the fact that everything is proper - and the next time you compile, it suddenly works again. That type of thing is normal.

I was originally planning to upload a nice little surprise to you all today, but I believe one of those little nasty gremlins have managed to infiltrate my code.

At first, it was just foolishness. I copied my data onto a multisession CD-R as a second session and move over to this computer - this computer can't read multisession disks, for whatever reason. At least not mine. Oh well, that type of thing happens.

Then I copy the files into an archive, the archive onto a floppy (well, not a real floppy, since nobody uses them these days, but a 3 1/2 disk), and then to this computer. Trying unpacking the archive - file corrupted. This type of thing happens.

I went back, used another disk, put the archive on there, moved over here - file corrupted. At this point I was starting to get slightly irritated. I went back and actually tested the disk - and the file worked properly. Okay, this type of thing apparently happens.

I reformated the disk, and copied the files onto it in a different archive format, came back, downloading the packer software and tried unpacking it... corrupted files again.

I decided to take the plunge and copied the files onto a brand-new spankling CD-R (well, I copied my entire non-BYOND programming stuff on there - no use in wasting a perfectly good CD-R), came over to this computer... and EVERYTIME I ACCESSED THE DIRECTORY WITH THE FILES IN IT, IT CRASHED THE BLOODY COMPUTER. All three times I tried it - the last by trying to right-click copy / paste without actually opening the directory. No good.

I could probably detail my last attempt to split my file into several disks and bringing them over, but needless to say, corrupted files.

Either my program is cursed, or this operating system here hates my program, for whatever reason. Well, I can understand it, considering that it was made with a programming language from a rival company, but still.

Tomorrow I'll try it from yet another computer. If that crashes when trying to access my CD, I know that I've managed to program a monster.

... and I was so excited for the unveiling...

splatty