Well, mine was one of the Vx's that the diagnostic utility flagged as being defective (Serial 50GK14G....., assembled in malaysia if anyones interestd). Patch applied and things seem to be working fine (although I hadn't noticed any problems anyway). My take on the problem is that there was a batch of 8MB memory chips which couldn't hold their state for the usual memory refresh time. The patch causes the memory to be refreshed more often (thus shortening battery life), and may possibly blank out sections of memory from being used (I seem to have lost 60K of memory even though the RefreshFix was only 19K). Anyone feel that Palm should be offering to replace affected Vx's? This is a manufacturing defect after all.
If I recall, System Shock was released in September 1994.
Marathon was originally designed as the sequel to Pathways Into Darkness (released August 1993) and was first shown at MacWorld SF in January 1994. Marathon went through a number of rewrites during 1994 with it looking very similar to it's final incarnation by August and released in December 1994. I don't believe Bungie took much influence from System Shock.
Unfortunately, the desyncing problem existed in all 3 Marathon games and was never fixed. The Marathon series used a very simple form of networking where each machine would play the game, and only the key-press/mouse-event codes were sent between. Effectively, each client thought that it had 8 keyboards attached to it. This method works fine if all data packets get delivered in the correct order and without delay, but if a couple of packets go missing, one machine may miss that keypress where I sidestepped out of the way of the incoming rocket, and from that point on, the game will look very different on each machine. The only way to avoid this would be to rewite the networking code in a client/server mode.
I don't know the height the satellite is above the moon so I don't know the speed exactly. I would guess that orbiter is at least 50-100 miles above the surface and is probably travelling from 7-15,000 km/hr. Does this sound right? Lunar Prospector recently dropped from it's mapping orbit of ~100Km to something like 25Km. Orbit time is around 1hr 40min, so I figure a speed of ~6500kph. It should leave a dent.
Slashdot Mirror
Well, mine was one of the Vx's that the diagnostic utility flagged as being defective (Serial 50GK14G....., assembled in malaysia if anyones interestd). Patch applied and things seem to be working fine (although I hadn't noticed any problems anyway). My take on the problem is that there was a batch of 8MB memory chips which couldn't hold their state for the usual memory refresh time. The patch causes the memory to be refreshed more often (thus shortening battery life), and may possibly blank out sections of memory from being used (I seem to have lost 60K of memory even though the RefreshFix was only 19K). Anyone feel that Palm should be offering to replace affected Vx's? This is a manufacturing defect after all.
If I recall, System Shock was released in September 1994.
Marathon was originally designed as the sequel to Pathways Into Darkness (released August 1993) and was first shown at MacWorld SF in January 1994. Marathon went through a number of rewrites during 1994 with it looking very similar to it's final incarnation by August and released in December 1994. I don't believe Bungie took much influence from System Shock.
Unfortunately, the desyncing problem existed in all 3 Marathon games and was never fixed. The Marathon series used a very simple form of networking where each machine would play the game, and only the key-press/mouse-event codes were sent between. Effectively, each client thought that it had 8 keyboards attached to it. This method works fine if all data packets get delivered in the correct order and without delay, but if a couple of packets go missing, one machine may miss that keypress where I sidestepped out of the way of the incoming rocket, and from that point on, the game will look very different on each machine. The only way to avoid this would be to rewite the networking code in a client/server mode.
Or, here to be more specific.
I don't know the height the satellite is above the moon so I don't know the speed exactly. I would guess that orbiter is at least 50-100 miles above the surface and is probably travelling from 7-15,000 km/hr. Does this sound right?
Lunar Prospector recently dropped from it's mapping orbit of ~100Km to something like 25Km. Orbit time is around 1hr 40min, so I figure a speed of ~6500kph. It should leave a dent.