ZylonBane on 2/12/2007 at 17:17
I can't imagine why you'd think it would.
Enchantermon on 2/12/2007 at 20:32
Mmm.....well, humor me. If I'm reading the FAQ right, then SS2 searches for the nearest available disk space and then checks 2GB starting from there. If the disk were defragented, then all of the available space would be at the end of the drive.
Theoretically, of course. Since files are being read and written all the time, it wouldn't stay defragmented for long, but in an ideal world, would that not work?
Or am I reading the FAQ wrong, and it's saying that SS2 only sees the first 2GB of the disk, not the first 2GB with available space?
ZylonBane on 2/12/2007 at 22:14
Windows apps do not touch the hard drive directly, ever, unless they're disk management software like Partition Magic. That's what the Win32 API is for. And SS2 uses an obsolete version of the Win32 free disk space call that doesn't understand disk sizes larger than 2GB.
Nameless Voice on 2/12/2007 at 22:39
I think it basically returns the free space modulus 2gb.
So, saving or downloading an extra 50mb of file(s) should make the free space 'wrap' back around and be detected correctly.
Example:
2050mb % 2048mb = 2mb of free space detected by SS2
2000mb % 2048mb = 2000mb of free space detected by SS2.
(For those who don't know, modulus (for which I've used %) yields the remainder of an integer division.)
Displacer on 3/12/2007 at 13:04
This error is because of a windows API call. It is not a bug because it was the correct call to use when this game came out. The call is GetDiskFreeSpaceA, which has a problem with large disks (search online for this call to see the details). The skip_starting_checks config item bypasses a call to _CheckForDiskspaceAndMessage which contains the API call. This however just skips the call when the game starts up, it does not skip it for saves, so you can still get this error when you save.
As I said I fixed this error once and for all, for startup, loads, saves, and any other disk activity this game uses. I made the fix for Kolya (a member here). I don't know what he did with it, but he is the one to ask because after I came up with the fix and passed it to him, I promptly forgot about it and as scatterbrained coders are wont to do, I neglected to write down what I did...
michaelg on 3/12/2007 at 16:53
Well as I said, I had a problem until I added the skip_starting_checks line to both the cam config file and the default_gamesys shock2.gam folder.
However I'd still like to know why, if I changed nothing on my comp from the previous day, I had any problems in the first place.
BTW; I don't believe the defrag thing makes a difference because I do that on a regular basis. It's the screwy haunted game that causes all these problems.
dvwjr on 4/12/2007 at 05:37
Quote Posted by Displacer
This error is because of a windows API call. It is not a bug because it was the correct call to use when this game came out. The call is GetDiskFreeSpaceA, which has a problem with large disks (search online for this call to see the details). The skip_starting_checks config item bypasses a call to _CheckForDiskspaceAndMessage which contains the API call. This however just skips the call when the game starts up, it does not skip it for saves, so you can still get this error when you save.
No need to patch Win32 executables to fix the deprecated
GetDiskFreeSpaceA API problem on Windows 2000, XP or VISTA. Just use the (
http://www.microsoft.com/downloads/details.aspx?FamilyID=24da89e9-b581-47b0-b45e-492dd6da2971&displaylang=en) Microsoft Application Compatiability Toolkit v4.x or 5.x with the fix
(shim):
EmulateGetDiskFreeSpace selected and installed for the System Shock 2 executable. This ACT fix provides the following support:
Quote:
This compatibility fix causes the Windows XP version of GetFreeDiskSpace to return values similar to those returned by Windows 9x. It hooks the GetDiskFreeSpace API and determines the true free space on FAT32/NTFS systems. If the free space is larger than 2GB, the compatibility fix will return 2GB as Windows 9x would return. If it is smaller than 2GB, it converts the sector geometry to emulate Windows 9x. Applies to: Windows 95, Windows 98
Hope this helps,
dvwjr
Kolya on 4/12/2007 at 20:38
Clearly the easier solution to clicking a checkbox in SS2 Tool...
metal dawn on 10/12/2007 at 00:44
I have a "odd" problem of my own.
Somehow, the mouse's functions are functioning independently.
I'll try to describe this the best I can...
The mouse buttons' function should work differently and separately depending on whether the MFD is open. My problem is that my guns fire regardless of whether or not my MFD is open. I can't pick up and drag any objects at all and can't examine or manipulate them (ie, right-clicking on my gun to modify it).
However, some function of right-clicking still work somehow. I can still bodies and such.
I have no idea how or why this is happening.
Thanks in advance.
