Telnet

Say I love to go on MODs but for some reason my computer is having trouble with Telnet. It would run fine for a bit like 20 to 40 mins but then it would crash and my cpmputer would go into safe/dos mode. I am gona stop using it but I want to know what's the heck is going on.. Has anyone have this problem?

Not once on my end, because I am a Mac user.

Anyway, which Telnet app are you using? Is it the built in stuff in the DOS Command Prompt? Or a 32Bit Windows native Telnet app? besides, befoer I became a Mac user, I was a DOS/Windows user. I stopped officially using DOS/Windows back in 1995 when I bought my first Mac, a PowerMac 7200. I followed this by an iMac in 2001, iBook in 2003 and a mew lates Mac a Mac Mini in 2006. Sorry to ramble off like some kind of Macintosh FanBoy, but I do have some experience in the PC front. I'm even going to install a dual booted Windows Vista copy into my Mac Mini later this year to broaden my Digital Media Design future.

It's the Windows system 32, is that a so called updated version. I would use a client but I find Telnet faster..

Forgive that, I refer to 32Bit as Windows system 32. Perhaps your use of Telnet through DOS is screwing it all up. I'd recommend you check these out at http://www.thefreesite.com/Free_Software/Telnet_freeware/

Try and use one of those freeware telnet clients. I remember that I had a similar telnet problem before I stopped running Windows 95.

Thanks but no thanks, I rather not. I'll just go on at the campus comps..

Btw, you said you had the same problem. what happened to you..?

Also I did changed the properties so I hope that'll fix it.

Jayn, that was nearly 12 years ago...I have a good memory, but not that good. Besides, I have been immersed in the Apple Macintosh world since then. All I know is that compared to the new UNIX command line of OS X, the telnet app is basically the same. As for what I did? I stopped using my Windows computer when it did nothing but give me Blue Screens all the time.

If its your choice not to use a client, than all the power to you 8) . I myself prefer command line applications for ftp and telnet use as well. Let me know if your changed properties do anything.

Right now however under Mac OS X TIGER, i'm using Cantrip for telnet access. Cantrip is of course a client, but it has been specifically designed for MUDs and MUCKs.

That's what mine does, if I run Telnet and when it crashes a blue screen would appear with a message saying that windows had shut down to prevent damage.. When I rebot it is fine. But should I be worried though, I mean can it damage my computer?

Holy crap, Jayn. You should be worried. A Blue Screen of Death caused by Telnet? Then there must be something seriously wrong with your Command Prompt. BTW, what version of Windows are you using?

I'm using Windows XP and I'll make a note about not using Telnet. My computer seems ok though, when I restarted my compuer windows came on and a windows message showed up saying that windows had recovered from a serious error. This had happebed a few times and when rebooted my computer restared just fine. And I have restarted my computer a few times since then and I'm not getting any error message or blue screens and it is working this fine..

I'm using Windows XP and I'll make a note about not using Telnet. My computer seems ok though, when I restarted my compuer windows came on and a windows message showed up saying that windows had recovered from a serious error. This had happebed a few times and when rebooted my computer restared just fine. And I have restarted my computer a few times since then and I'm not getting any error message or blue screens and it is working this fine..

If you are getting blue screens under Windows XP, you're almost certainly having either a hardware problem or a driver problem. Telnet is almost assuredly not causing it, at least not directly.

That sounds about right. Being either hardware or driver errors. I don't see how using Telnet in command prompt would be triggering hardware/driver errors, but thats one of the many reasons why I have no real affiliation with Windows anymore.

I'm definately no expert with operating systems and all that. But from the sounds of this, it makes me suspect a conflict with network drivers or something.

--Tzol

Most likely. The best option that pops to my mind is making sure that the network adapter's drivers are up to par. As you all know, I am a Mac user. I had a similar problem with using the command line ftp app in my terminal. Terminal UNIX command line app in Mac OS X. FTP was crashing terminal almost all the time a few years ago when I was running OS X Panther. It was suggested to me from a few fellow OS X friends to make sure that my computers firmware and network drivers were up to date. So I downloaded the latest firmware update and found a newer driver version for my iBook's slightly older Network adapter. For me, it fixed the problems I was having. This was one of the major reasons why I went Macward. If something happens with a single application, it only crashes the application and not the entire OS. Sure there are a lot of Mac applications that are known to crash, but i've never had a crashed app kill OS X completely and force a restart. I only ever had to restart a Mac under pre-OS X systems like System 7 - 9.2.2 and these rarely had system crashs, but they happened a few times. I'm sure you can make Mac OS X crash, but you really have to do some really stupid things to the system logged in under the UNIX ROOT Account.

I'm definately no expert with operating systems and all that. But from the sounds of this, it makes me suspect a conflict with network drivers or something.

--Tzol

If you don't have these problems while doing normal web-browsing, however, I wouldn't be so sure that it's the network drivers; telnet and web traffic should look almost identical to a network card. However, unless you can give more specific information about what the blue screen says (like the specific error message or something), then all of this is a shot in the dark.

Whatever the reason for the blue screens, I hope you get it fixed soon, Jayn.

Yea I'll just stop using Telnet, it sucks anyway. I do find I have a small problem, when I try to run Disk clean-up I get a "program had enconter a problem and needs to close." I'm prettey sure it's not because of windows shutting down otherwise I have error messages pooping up at me and I ndon't..

Hmm, sounds strange to me. Now i'm lost, sorry I can't be of any further assistence Jayn, but as mentioned before I am crap when it comes to PCs since I have been a Mac user for 12 years. I really do hope you get it fixed soon.

You know something wired, it doesn't do it all the time. Some nights it'll run just fine, I do have one of those wireless connectiuons.. Could that have something to do with it..?

You know something wired, it doesn't do it all the time. Some nights it'll run just fine, I do have one of those wireless connectiuons.. Could that have something to do with it..?

Hmm, I really don't see how that would effect the performance of Windows XP unless your wi-fi card has either old drivers or something else completely different is going on.