Pugugly001 wrote:Bought Uplink (again) from GOG, having fun, and I think I got caught out by a bug attempting to hack a bank - First it wouldn't allow the transfer despite bypassing the proxy, then after I figured out that was probably a bug and tried it again,...
I doubt this was a bug. Were you using the highest level proxy bypass?
Pugugly001 wrote:...the bank picked up the trace only two hops from home (and to be fair, I hovered over the disconnect button a sec too long trying to decide if the proxy was going to fall in time for me to click 'transfer; before disconnecting).
So this once I'm just irritated enough to try and reinstate my savegame, but the only tool I can find dates from 2007-ish and requires (coff coff) .Net 1.1.4322.
"Permadeath" is part of the game. You waited too long, got caught, game over. That is as intended. Start a new game---if you know how to play, it doesn't take that much time to get back to where you were (the entire story arc can probably be completed in less than 30 minutes by someone who really knows what they are doing).
Pugugly001 wrote:Assuming even Indiana Jones can't recover a version of .Net 1.1.4322 that runs with Windows 10, am I just done or is there a way to reinstate this? And can anyone confirm there is/is not a bug when the Bank suddenly jump 95% of a trace?
There are a couple of things to keep in mind: (1) banks have very good security, and will trace you faster than most other systems, and (2) different servers that you bounce through require more or less work to trace through---if you have root access to a server, you can delay the trace longer, while insecure servers will give you up much faster. If you last bounce was, for example, through InterNIC, then it is no surprise that you got caught.