ok, i've been stuck with this for about 2 days now. I have 2 missions which are both being exremely annoying. Both of them are to destroy all the files on a server. So what i did, was open up trace tracker, have about 7 or 8 banks, and hten 5 other links or so, being bounced (with the first bounce point being internic)(with these certain bounce points i get about 180 seconds to do my work). Then i connect, open up the connection analysis, place my proxy disable, monitor disable, and firewall disable. Then i use the password breaker to get in. I go to admin, console, i type in "cd usr" and then "delete" and then "exit". Then i delete the logs at the server (everyone of the logs except the most recent "established" log. I then disconnect, go to Internic, and delete the routed and password acceptd logs (so that there are only closed and connection extablished logs left, with a connection established one being the most recent). Ok, so i go to the internal server of uplink, and hit fast forward a bit, and the news pop-ups that a certain server's files were deleted. So i go to my email, and respong. I get a responce saying my mission was a success or whatever. And then acouple minutes later, it either (depending on whioch of the two i'm stuck on) uplink disavows me (or however you say it), or gives me a warning and says that it won't let me go back to that server. I don't get it, i've looked for the answer everywhere. Is it a bug? am i forgeting something, am i just really slow?

------------------

I don't know if this might work but try this, make your second connection the Uplink Test Machine and then delete those logs after you brake in to the machine.

Also when you are in the control console deleteing the files insted of exiting type cd .. then cd log and delete.

You can also try just getting the password then disconecting deleting the logs on the InterNIC and Test Machine. Then go back and complete your mission.

------------------

Altho TLAM Strike may have solved the problem, I feel the need to contribute my knowledge to this. If you fallow the procedure for destroying the system, which is go to the terminal and type: cd usr, delete, cd sys, delete, cd log, delete, shutdown, and then deleting your bounce at InterNIC, you will have effectively no chance of being caught.

------------------

Quote

Originally posted by TLAM Strike:
**I don't know if this might work but try this, make your second connection the Uplink Test Machine and then delete those logs after you brake in to the machine.

Also when you are in the control console deleteing the files insted of exiting type cd .. then cd log and delete.

You can also try just getting the password then disconecting deleting the logs on the InterNIC and Test Machine. Then go back and complete your mission.

**

If their 1st bounce is InterNIC and they're deleting those logs, there shouldn't be much reason to delete the logs at their 2nd bounce.

------------------
The box said Windows 95 or greater...so why doesn't it work on a Mac?