WinUAE serial options

[Steady]

Hi all,

i was wondering if anyone has a clue how to enable the telnet serlal output in WinUAE and get it to work.

All I ever see as options for the serial port are "none" and "TCP://0.0.0.0:1234".

Even if I set option in the config file to an IP address and port, it can't be selected and doesn't work. I'm obviously missing something.

Any clues???

[Thomas]

This acts as a telnet server, not a client. If you set it to tcp://0.0.0.0:1234 and start WinUAE, it will wait until someone connects to port 1234. For example you can open a DOS window and enter telnet localhost 1234. Then WinUAE will start and everything which is written to the serial port by Amiga programs is shown in the telnet window.

[Steady]

Thanks Thomas.

Actually, it didn't seem to wait, maybe serial output does. I will test it out.
Thanks for the pointer.

[Steady]

Hey, I got it working thanks to your advice!!! :-)

Cheers.

[Duce]

Good advice and works a treat for running a BBS on a UAE machine with the proper .device

[ChaosLord]

This acts as a telnet server, not a client. If you set it to tcp://0.0.0.0:1234 and start WinUAE, it will wait until someone connects to port 1234. For example you can open a DOS window and enter telnet localhost 1234. Then WinUAE will start and everything which is written to the serial port by Amiga programs is shown in the telnet window.

@Thomas

I just want to be clear about this.

I just bought a brand new bgcpc 3.1Ghz core i5 to hopefully do Amiga dev using the freeware opensource WinUAE Amiga Virtual Machine.

My new pc does not have a real serial port.

Thomas, can I use your trick so that debug output from my Amiga debugger will go out of WinUAE Virtual Amiga into my Windoze 7 DOS window?

I hope this will work!
I haven't been able to set up the new puter yet.  Hopefully in some weeks it will happen and I am really thankful for your advice!

[Thomas]

Yes, that's how it's supposed to work.

However, you have to intend to write low-level system drivers if you need debug output to come out of the serial port. In all other cases you can use Sushi or Sashimi to get debug output into an AmigaDOS window.

[ChaosLord]

Yes, that's how it's supposed to work.

However, you have to intend to write low-level system drivers if you need debug output to come out of the serial port. In all other cases you can use Sushi or Sashimi to get debug output into an AmigaDOS window.

Of course I have used Sushi/Sashimi for many years.  But sometimes a bug crashes the whole Amiga and I lose my Sushi window.  If I had a system set up so that I never lose my MuGuardianAngel output then I could save many hours of debugging time.

I have another Amiga that I could connect to the serial port but  I never got around to it.  Lame me.

It seems easier to do it all on 1 machine.


p.s. My Rosewill keyboard ERASED my whole msg and I had to retype the whole thing.  It has a defective connector that shorts out all the time.  Never buy a Rosewill keyboard ever!  They built it this way on purpose.  Even after thousands of complaints of this exact same problem they keep making them defective and selling the defective keyboards.

[Duce]

Can echo the comments on Rosewill keyboards flaking out.  Had one, was real nice, mechanical keyboard - worked jsut aces for a month or two, them just went belly up.  Shame really, Rosewill PSU's are pretty good, but wouldn't recommend the keyboards.

Went with a Corsair K 90 Vengeance mechanical gaming keybd after that one and it's a real keeper.  Pop the keys off every month or so for cleaning and not a problem thus far.

(sorry for the OT post!)

[ChaosLord]

Can echo the comments on Rosewill keyboards flaking out.  Had one, was real nice, mechanical keyboard - worked jsut aces for a month or two, them just went belly up.  Shame really, Rosewill PSU's are pretty good, but wouldn't recommend the keyboards.

Went with a Corsair K 90 Vengeance mechanical gaming keybd after that one and it's a real keeper.  Pop the keys off every month or so for cleaning and not a problem thus far.

My Rosewill keeps going off and on real quick so it will drop a char or 2 here or there.  The lights flash off and on at me like its demonically posessed.  Today it keeps thinking the shift key is stuck down.  When that happens, every thing I try to do in Chrome goes completely haywire!  My mousewheel stops working, giant blocks of text keep getting marked, everything just goes bonkers.  I keep jiggling the cable to make it work.  Then I have to repeat the process every 5 mins.  I have only had this Rosewill keyboard for 37 days.  I would like to get a little more use out of a $70.00 keyboard.   Its an ez solder fix.  But I can't solder.  Period.  So what's a lamer like me to do?

I really love the cherry red switches.  And I have my super soft foam crashpads under every key so its a soft squishy nonpainful typing experience.  That is the only reason I can write these giant messages.  If I send the keyboard back I lose everything.

I love being able to type msgs to Thomas.  He always has all the handiest tricks.  For 4 years I could not type jack.  It suxxed so bad.


Back to the Serial Port Topic
Is there anyway for me to redirect SER: access to PAR: on my real A1200T?

My A1200 and A3000 are already networked with PARnet.  PARnet is really super fast when being driven by an 060.  I forgot the speed off the top of my head but it was something like 8x faster than 120000baud.  You can copy 10 floppy disks over just like that.  Bzap!

It would be way kewl to send my debug output to my A3000 over PAR:
Sometimes I will get 100 MuGuardianAngel hits in a row and it pretty well stops my Amiga from working while all that text is redirected thru Sushi to my shell window.   Seems like it could be faster if it went to PAR:

I think sometimes I crash the Amiga before all the text can even get printed.  There is a big backlog.

[Steady]

@ChaosLord

Like Thomas said, that is what it is for. You don't need an actual serial port which is why I was trying to get it working. I tested it with ROMWack and it worked fine. I used a separate telnet program on windows rather than the command-line version connecting to localhost:1234 and all was good as suggested by Thomas.

... not sure about redirecting SER: to PAR: but if you are doing your own debugging, just use the parallel port version of the debug lib. I think it's ddebug.lib using a prefix of "d" instead of "k" for the function names.