start the BBS, I am getting the popup saying that the virtual com port
is in use when it really isn't. If I ignore through the error boxes,
the BBS starts up just find and runs normally.
* An ongoing debate between Robert Wolfe and All rages on ...
start the BBS, I am getting the popup saying that the virtual comport RW> is in use when it really isn't. If I ignore through the
error boxes, RW> the BBS starts up just find and runs normally.
I get one of these in my WinXp32 VM using Mystic, but it doesn't
affect anything that I can see going on, so I just dismiss it {shrug}
let me know if you discover the cause! :)
Now if anyone has a working ISO of the latest OS/2 Warp 4 FixPack they would not mind sending me, I can give them access to my FPT server (running an OS/2 FTP server package called FtpServer by Peter Moylan).
Hi all!
Well, it looks like I got OS/2 Warp 4 installed in a VM and the BBS working with SIO 1.60d and VMODEM. Unfortunately, whenever I go to
start the BBS, I am getting the popup saying that the virtual com port
is in use when it really isn't. If I ignore through the error boxes,
the BBS starts up just find and runs normally.
Unfortunately, this popup is an annoyance when trying to run a front
end mailer (ViaMail in this case) and it goes to load the BBS and the
BBS exits back out to the mailer when a caller logs off.
--- ViaMAIL!/WC v2.00
* Origin: ViaMAIL! - Lightning Fast Mailer for Wildcat! (1:261/20)
Well Maybe I can explain a bit but who knows?
Well, it looks like I got OS/2 Warp 4 installed in a VM and the BBS
working with SIO 1.60d and VMODEM. Unfortunately, whenever I go to
start the BBS, I am getting the popup saying that the virtual com port
is in use when it really isn't. If I ignore through the error boxes,
the BBS starts up just find and runs normally.
Unfortunately, this popup is an annoyance when trying to run a front
end mailer (ViaMail in this case) and it goes to load the BBS and the
BBS exits back out to the mailer when a caller logs off.
I think few people have much knowledge of how OS/2 handles actual IRQ numbers and ring level work that are really needed for carrying OS/2
back to way before even DOS operations for some things. For example, 'normal' IRQ top level stuff only applies to IRQ 'numbers' up to what I think I recall are number 8. That's not enough to work with some
things that we need for IRQ level numbers which go up even way beyond number 8 especially when OS/2 is 'later' dealing with multiple CPU operations that, as I think I recall this, are up to as many as sixteen separate CPU's which then must be able to be coordinated with each
other as to what each CPU is doing that must be absolutely understood
by any action even down to COMM ports so that things don't violate the order of operation for multiple CPU stuff that grew up long after the original ring level and machine language code which I was originally working with LONG before there was OS/2 even there.
Sysop: | DaiTengu |
---|---|
Location: | Appleton, WI |
Users: | 991 |
Nodes: | 10 (1 / 9) |
Uptime: | 126:55:00 |
Calls: | 12,960 |
Calls today: | 2 |
Files: | 186,574 |
Messages: | 3,265,879 |