[Search for users] [Overall Top Noters] [List of all Conferences] [Download this site]

Conference hydra::amiga_v1

Title:	AMIGA NOTES
Notice:	Join us in the NEW conference - HYDRA::AMIGA_V2
Moderator:	HYDRA::MOORE

Created:	Sat Apr 26 1986
Last Modified:	Wed Feb 05 1992
Last Successful Update:	Fri Jun 06 1997
Number of topics:	5378
Total number of notes:	38326

1161.0. "FOGGY hi baud rate upload bug?" by WJG::GUINEAU (W. John Guineau, RD Buyout engineering) Fri Feb 12 1988 08:16


I had some strange problems last night while trying to upload files from
Amiga to a local MicroVAX. The Amiga is hard wired to the �VAX, I'm
using Foggy x1.0.

I can download at 19200 baud to floppy or RAM with no problems. When I tried
to UPload at 19.2K, XMODEM (Amiga side) would hang for a few minutes after the
file transfer window poped up, then say "no acknoledge" and abort. on the VAX
side, at this point XMODEM would exit with some funny characters on the screen
and then get back into the program as if I had hit "up arrow" and pressed
return!

I figured it was something to do with the transfer going faster than data
comming off the floppy. So I tried using RAM. Same thing. XMODEM would
hang... then abort. KERMIT would hang Amy (mouse wouldn't even move!)

This was consistant at 19.2 and sporatic at 9600...

Anyone have any clues?  (it seems like the XMODEM/KERMIT on the VAX side
is not dealing with high baud, but then with old SMOKEY I've uploaded at 9600
even from floppy...

Has FOGGY upload logic and/or baud rate code been changed? (I know the
baud stuff has since SMOKEY didn't support 19.2 and 38.4)

John

T.R	Title	User	Personal Name	Date	Lines
1161.1		EVER11::EKLOF	We're everywhere.	`Fri Feb 12 1988 12:18`	11
	Re: .0 >Has FOGGY upload logic and/or baud rate code been changed? (I know the >baud stuff has since SMOKEY didn't support 19.2 and 38.4) You're kidding, right? I didn't change any of that. Support for 19.2 and 38.4 K baud were in Smokey X1.0. All I changed in Foggy was the keyboard handling. Mark
1161.2	What kind of microvax port are you abusing?	PRNSYS::LOMICKAJ	Jeff Lomicka	`Fri Feb 12 1988 12:41`	14
	What kind of serial port were you using on the microvax? Were you using the console port? The console port takes an interrupt per character, and the VAX just might not be able to keep up. I've found that even when tyou set /ALTTYPEAHEAD on the port, which helps a lot by the way, that I cannot reliably use KERMIT on CSA0: of a microvax at speeds over 4800 baud. You get problems with data overruns because there is no hardware buffering in the console port. If you have a DZV or DZQ, then setting /ALTTYPEAHEAD on the port should cure the problem. Make sure the sysgen parameter that controls the /ALTTYPE size is set to something large enough, at least 256. (I use 2000). Note that setting /ALTTYPEAHEAD requires /PERM, which requires that you have sufficient privs.
1161.3	2000 you say?	WJG::GUINEAU	W. John Guineau, RD Buyout engineering	`Sat Feb 13 1988 18:24`	9
	It's a DZQ. I bet /ALTYPEAHEAD is the culprit! Privs? Why, I wouldn't use a MicroVAX without 'em ! Thanks Jeff, John (who's logging out now to fix his MicroUploader)
1161.4	Like Magic	WJG::GUINEAU	W. John Guineau, RD Buyout engineering	`Sun Feb 14 1988 09:55`	7
	And that floppy dosen't stop spinning till it's done! Thanks Again Jeff, John
1161.5	38.4	DICKNS::MACDONALD	WA1OMM Listening 224.28	`Sun Feb 14 1988 19:12`	4
	Smokey doesn't handle 38.4 very well. Either that or my PC running ProComm Plus doesn't handle it well. Paul
1161.6		WJG::GUINEAU	W. John Guineau, RD Buyout engineering	`Mon Feb 15 1988 08:51`	12
	After poking throught the Libraries and Devices RKM manual, I found that the Amiga HARDWARE supports up to 220,000 BAUD! Except that due to the multi-tasking nature, recieving is only relaible at 19.2 or slightly above (I think something like 31000 is max) Above that you may loose a character here or there :-) You can send as fast as you'ld like - assuming your software can keep up. John
1161.7	meshugena	VIDEO::LEIBOW	Michael Leibow	`Tue May 31 1988 18:32`	8
	There is also a problem with the serial.device driver (or my ignorance about something): Sometimes at high baud rates, the Amiga will send out 4 XOff characters and never send an XOn. --Mike Leibow