8 replies
by lamentofking Accepted solution
by older mycroft Accepted solution
That you don't have sufficient space for all the Temp files that Halo will generate 'on the fly' AFTER it is installed, when you start to run it.
Microsoft games are notorious for using their own 'extra' space, just as Windows is.
1GB does seem a bit tight for anything that uses Temp files.
by older mycroft Accepted solution
Minimum system requirements
? Operating System: Microsoft Windows 98, Microsoft Windows Second Edition, Microsoft Windows Millennium Edition (Me), Microsoft Windows 2000, or Microsoft Windows XP.
? Computer/Processor: 733 megahertz (MHz) processor.
? DirectX: DirectX? 9.0 or later. (DirectX 9.0b is installed by Halo.)
? Memory: 128 megabytes (MB) of RAM.
? [b]Hard Disk: 1.2 gigabytes (GB) of free hard disk space.[/b]
? Video card: 32 MB with 3D Transform and Lighting capable.
? CD: 8X.
? Sound: Sound card, speakers, or headphones with multiplayer play.
? *56.6 Kilobytes per second (KBps) modem or 10 MB network adapter. Multiplayer servers require broadband to run a server.
? *Additionally, you must have an Internet Service provider (ISP) or a Local Area Network (LAN), if you want to play multi-player games.
Extract from:
http://support.microsoft.com/kb/829479
by lamentofking Accepted solution
by older mycroft Accepted solution
For argument's sake, let's suppose that Microsoft is talking about 1.2 binary gigabytes and Linux is reporting 1.25 decimal gigabytes then by my reckoning you don't have enough space.
If your allocated space within the Linux partition is presently occupied by "[i]Linux stuff[/i]" that you've downloaded, why not dump some of it out to an optical drive to free up another 1GB of space ?
Otherwise you'll be running round the houses all weekend looking for a solution that may not be attainable.
Is this 'Custom Edition' kosher ?
Because I've never heard of it. ;)
by lamentofking Accepted solution
by madlewtor Accepted solution
Even though your problem is slightly different than the one I experienced, I managed to locate the missing files in the /var/crash/* directory. It seems that we had a scsi disk that was partitioned into several pieces and one happened to be a /var mount. As the system was being reboot, it would unmount /var and then crash. Linux stores crash dumps in /var/crash/* directory, and seeing how /var was unmounted, it still placed the files in that location (as expected). Upon rebooting the server, the system would once again mount /var over top of where the crash dumps were being saved. This resulted in the inability to "find" the missing disk space, even though the output from df was not correlating with the output from du -s when executed from /
I hope this helps someone.
by older mycroft Accepted solution
I can't help but feel that you've answered the wrong thread.
I fail to see what your answer has to do with this aged question.
This discussion is closed to new replies.
Trending Linux posts
Sort by Trending