Halo 1 & 2 for PC
This topic has moved here: Subject: Possible fix for failing installs after SP2 update.
  • Subject: Possible fix for failing installs after SP2 update.
Subject: Possible fix for failing installs after SP2 update.
  • gamertag:
  • user homepage:
  • last post: 01.01.0001 12:00 AM PDT

Are you having difficulty installing Halo after SP2 update? Does your install bum out reporting that it cannot copy sounds.map at around 80% complete? Fear not, there may be a solution! :-)

I experienced this problem after installing XP SP2 and also upgrading the firmware of my Plextor CD-ROM, I'm not sure which action was responsible for the bug. I also installed an update to Nero, so this might also have affected the CD-ROM subsystem somehow.

I fixed my system like this:

1. Ensure that your local security policy does not have 'Clear virtual memory pagefile when system shuts down' enabled under 'Security Options' (this will ensure faster rebooting anyway, so is advisable to switch off unless you're ultra paranoid.) This option is not enabled by default, and probably never will be unless you're in a very secure networked environment. If you don't know what it is, then you don't need to fix it.

2. Delete the Windows page file. This can be done by accessing 'Administrative Tools' -> 'Computer Management' from the Control Panel. In the tree view in the left-hand pane, right click on the root node (Computer Management (Local)) and select 'Properties'. Click on the 'Advanced Tab' and then the 'Performance Options...' button in the 'Performance' control group. Now, click on the 'Change' button in the 'Virtual Memory' control group. Set both the initial size and maximum size to 0 MB (for each drive). Now reboot. Upson reboot, set your page file(s) back to system managed. Reboot again.

3. Set the transfer mode of your CD-ROM to 'PIO Only' (disable DMA). To accomplish this, start by accessing 'Administrative Tools' -> 'Computer Management' from the Control Panel. In the tree view in the left-hand pane, right click on the 'Device Manager' node. In the tree view in the right-hand pane, expand the 'IDE ATA/ATAPI controllers' node and right-click on the leaf-node which applies to your CD-ROM (commonly the 'Secondary IDE Channel'). Now select 'Properties' from the popup menu. Select the 'Advanced Settings' tab. Set the 'Transfer Mode' using the drop-down list box to 'PIO Only' for the applicable device (commonly 'Device 0', the 'master' on the secondary channel).

4. Attempt to install Halo from the original disc again. Install might be slow, but it should procede with no errors.

If you experience problems running some games, the following link might also be of interest: http://www.macrovision.com/products/safedisc/index.shtml. There is an update available I believe.

Good luck!

Cool cool.
s.c. :-)

P.S.
Spread the word, I think alot of people will be encountering this problem. Microsoft do have a KB article out on this issue, but it's obscure and most gamers won't find it. These procedure apply to any install which fails to copy large CABs.

  • 12.01.2004 3:34 AM PDT
  • gamertag:
  • user homepage:
  • last post: 01.01.0001 12:00 AM PDT

1.Try getting rid of sp2. The only thing sp2 does is install a crapy firewall, get a better one. If u have nortan 2005 the internet worm blocker is also a firewall.(or just go and buy a good one)
2. Nero won't effect the cd drive. The firmwire upgade could have done it.
p.s if u are behind a router u won't need a fire wall

  • 12.01.2004 6:20 AM PDT
  • gamertag:
  • user homepage:
  • last post: 01.01.0001 12:00 AM PDT

Actually, CD burning software can give grief to some people. A classic complaint is "vanishing drive" syndrome. Basically, the device manager will report that it cannot load the drivers for your CD drive(s) even though you know damn well they're on your system (error code 39 I think). This actually happened to me after messing with Nero recently on a Win2k machine at work. The common solution is as follows:

Delete the upper and lower filters keys in the registry here:

HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Control\Class\{4D 36E965-E325-11CE-BFC1-08002BE10318}

BTW, I know a bit about firewalls. I have a cisco box in my rack at home. I don't have a problem with multiplayer aspects of Halo, that is an elementary configuration issue. It was installing the game in the first place which wasn't gonna happen on my patched XP system. :-)

Cool cool.
s.c. :-)

P.S.
A silly bug I noticed playing Halo on someone elses machine:

I use a Matrox Parhelia at home, which works very nicely despite not being fully supported in-game (looks great playing Unreal 2004 across 3 monitors with superwide FOV though!) The machine was running a Sapphire Radeon 9200 Atlantis 64MB + latest Cat drivers. Players who'd picked up "invisibility" showed up as white 'cos the textures were screwed. This is now in my list of useful bugs I don't want to fix. ;-)

  • 12.01.2004 9:59 AM PDT