COMM port support somethings got fixed?

DOS specific questions.
MystikShadows
Posts: 612
Joined: Jun 15, 2005 13:22
Location: Upstate NY
Contact:

COMM port support somethings got fixed?

Postby MystikShadows » Oct 19, 2008 16:38

I didn't read about them in the change logs.

Bit code I wrote for 0.18.3 now seem to work as expected in 0.20.0. So I'm asking coderjeff or anyone else that might know, if anothing was changed concerning comm support in 0.20.0 or if other statements like file manipulation PRINT #1, LINE INPUT #, GET #, etc etc..have been updated to work better with COMM in some way shape or form?

I don't mind, i'm glad to see it work, but I just didn't read anything about this in the 0.20.0 release notes, yet it's the same code, compiled with 0.20.0 running on the same hardware performing the same task on the same comm port that now works where it wouldn't the last time I tested the code.

Anyone have any idea? :)

Thanks
stylin
Posts: 1253
Joined: Nov 06, 2005 5:19

Postby stylin » Oct 19, 2008 16:45

MystikShadows, I found this in the changelog:
Version 0.18.4 Beta:
...
[fixed]
...
178 - lang qb: OPEN not handling COM/LPT device names correctly (jeffm)
...
180 - OPEN COM protocol parser was not handling default parameters (jeffm)


Perhaps one of those fixes is what you're looking for.
MystikShadows
Posts: 612
Joined: Jun 15, 2005 13:22
Location: Upstate NY
Contact:

Postby MystikShadows » Oct 20, 2008 0:34

Wow, that's what I get for readign changlogs at 5AM before my first 5 cups of coffee. lol.

Thanks stylin, I thought I paid attention when I read that, but obviously, I wasn't lol.

Well, let me say that those changes probably did (i'm thinking the default parameters issue probably did the trick here.

Thanks Jeff. :)...I and probably others appreciate that. :)

Return to “DOS”

Who is online

Users browsing this forum: No registered users and 17 guests