Your browser does not seem to support JavaScript. As a result, your viewing experience will be diminished, and you have been placed in read-only mode.
Please download a browser that supports JavaScript, or enable it if it's disabled (i.e. NoScript).
A lot of folks here mentioned the LAN-bug. Indeed the LAN-mission (e.g. the LAN itself) is extremely buggy.
This makes LAN-Hacking always an adventure...no Beer and no TV make Homer crazy! Fix it please!
------------------
What do you mean "Fix it please!"? Do you mean fix the fact that some LANs are harder than others? It is supposed to be like that.
But as for the other problems... well, I have never had Uplink crash, but I have MUCH experience with the LAN_Probe bug.
In any case, the beta testers are aware of these bugs (as you might notice by looking at the posts regarding 1.3.2 bug). If you have a new bug, post it there. If not... leave it alone for now. They are probably working as fast as they can.
------------------ "Always listen to the experts. They will tell you what can't be done, and why. Then do it." - The Notebooks of Lazarus Long There are things more annoying than using MS Windows... but I can never remember what they are. -Me
Ok,ok...I 'll never complain again about the Crash- and Probe-Bug! I promise and apologize. But the last one of my "complains" is meant as it was written: there occur LANs wich ARE impossible to hack! Example: I entered a LAN (with the best hardware and software uplink has to offer, all works fine on ather LANs) and scanned it, probed it and: There's a Router, some HUBs and a lot of Locks and Terminals. In the middle there's a Modem connected to a Isolation Bridge. None of the Terminals include a Modem Number. Other company LANs (I figured that trick, already) are not existing. So: I would need a Modem-No. to access the Isoöation Bridge. The LAN offers no chance to get this number...Aaargh. I really think that's a LAN wich is impossible to hack...am I soo wrong and stupid?
Are you sure you spoofed the terminals?
Yup. I spoofed every terminal, hacked each and every server...
To get the modem's number, connect to it (if you can, 'cause of the bridge). It'll give you the number. If the Isolation bridge block you, use the LAN_force on the lock, disconnect, erase the logs, come back. The lock is smashed down. The LAN_force should be used only if there's no other way to unlock a lock.
------------------ (url="http://"http://www.evula.com")EVula(/url) | (url="http://"http://www.Evula.com/survival_guide")EVula's survival guide(/url) | (url="http://"http://pftn.evula.net")Pilot File Trade Network(/url) | (url="http://"http://www.ev-nova.net")EV-Nova(/url) | (url="http://"http://home.attbi.com/~slagblah/")Slagblah's home page(/url) | (url="http://"http://home.attbi.com/~slagblah/pilotlog.html")pilotlog(/url) (url="http://"http://www.resexcellence.com/support_files/resedit.shtml")ResEdit(/url) | (url="http://"http://w00tware.ev-nova.net/")W00tWare(/url) | (url="http://"http://www.ariossoftware.com/programs/evone/")EVONE(/url) | (url="http://"http://davidarthur.evula.net/mc.php")Mission Computer(/url) | (url="http://"http://home.attbi.com/~slagblah/PilotlogAnalyzer.hqx")Slagblah's pilotlog analyzer(/url) Visit my (url="http://"http://perso.wanadoo.fr/straven")home page(/url) ! STraven, creator of (url="http://"http://www.ambrosiasw.com/cgi-bin/vftp/show.pl?product=evn&category;=plugins&display;=date&file;=outfits_enabler_v1.1.sit")Outfit Enabler(/url).
(This message has been edited by STraven (edited 07-12-2003).)
Quote
Originally posted by STraven: **To get the modem's number, connect to it (if you can, 'cause of the bridge). It'll give you the number. If the Isolation bridge block you, use the LAN_force on the lock, disconnect, erase the logs, come back. The lock is smashed down. The LAN_force should be used only if there's no other way to unlock a lock. **
I'll take that as confirmation that LAN Force is sometimes neccessary. grr, truth not make happy.