• Welcome to Battlezone Universe.
 

News:

Welcome to the BZU Archive dated December 24, 2009. Topics and posts are in read-only mode. Those with accounts will be able to login and browse anything the account had access granted to at the time. No changes to permissions will be made to be given access to particular content. If you have any questions, please reach out to squirrelof09/Rapazzini.

Main Menu

PB4 Bug: AIP Autoreg files and MPI

Started by Steeveeo, July 11, 2008, 03:47:49 AM

Previous topic - Next topic

CmptrWz

Better to fix MM5, I think, and leave more options for people in the game.

OvermindDL1

Spaces are a correct part of pathnames and if something does not accept it then that means it is broken; the broken thing should be fixed.

Generated by OvermindDL1's Signature Auto-Add Script via GreaseMonkey


mrtwosheds

I hale from the old dos days. spaces were used between commands and parameters, they had no place in file names or directory names, I still stick to this old convention just to avoid problems such as this.

OvermindDL1

That was with DOS, the current Windows has no affiliation with DOS, but rather NT.  Actually it is because of the filesystem, FAT16 only allowed 8.3 filenames with no spaces, FAT16+ was the same as FAT16 but with names up to 256 in length, spaces are allowed (this came out with Win95).  FAT32 came out later on (Win98se I think...) which allowed everything FAT16+ allowed, but with larger volume sizes.  NTFS allowed even larger volume sizes, faster access, and could be set to run in two modes, the first being compatibility mode which it supported 256 characters for a full path, and supported an old 8.3 syntax for the older apps.  Native mode does not have support for the old 8.3 syntax, but sllows paths with a max length of 2048 characters.  Anything that has existed for at least a decade has no excuse to be broken like that due to programmer stupidity or lazyness.

Generated by OvermindDL1's Signature Auto-Add Script via GreaseMonkey


mrtwosheds

True.
I do find it very annoying though when somebody does actually use a file name of 2048 characters. Its a name, your supposed to be able to remember it, not a short story.

Nielk1

That's the full path...

I've had issues with files with long names downloading into a few sub folders and thus becoming inaccessible. I had to use a special invalid file deleter/renamer on them.

Click on the image...

OvermindDL1

Yes, full path.  I have had to access many files where they are so many folders deep that they exceed 512 chars, making them inaccessible to the compatibility mode (that windows turns on by default, mine is off), so have to shuffle around parent directories to fix them.  No issue since I run it in native now.

Generated by OvermindDL1's Signature Auto-Add Script via GreaseMonkey


Red Devil

How do you turn off compatibility mode?
What box???

OvermindDL1

Some setting in the registry, set it like three years ago and still running the same XP install (I think it is going on 5 years, man I can keep windows running fast... :P ).

Generated by OvermindDL1's Signature Auto-Add Script via GreaseMonkey