@MSGID: 2:362/6 00080b7e
Maybe you could find an OS/2 Warp 4 installation kit = 2 CDs
somewhere.
If somebody makes ISO images and posts an Emule link, maybe I can ...
There are however a couple of fixpaks to be considered but I do
have them. So far I haven't needed them.
Those too.
The only solution would be to run old hardware, CPU <= 350mhz.But JK>that's hard to find nowdays, even on Ebay.
That is a good solution. The OS/2 Warp 5 operating systems
requires very little processor power and occupies only 120 Mb on
the HD. That means that you have plenty of space even in a 1 Gb
partition.
Not so good really. Motherboards of that vintage are 20 years old
now. That exceeds the life expectancy of the electrolytic capacitors JK>onboard. They can be replaced at small cost, if you can do the job JK>yourself, but it requires steady hands and good eyesight.
I solved the problem by running OS/2 WARP as a guest operating system
under VMware's VM workstation product. I've got OS/2 WARP 3 running
PCBoard sitting on a Windows 2008 R2 server as a guest VM. I no
longer have to worry about hardware. I only support telnet access.
I solved the problem by running OS/2 WARP as a guest operating
system under VMware's VM workstation product. I've got OS/2 WARP 3
running PCBoard sitting on a Windows 2008 R2 server as a guest VM.
I no longer have to worry about hardware. I only support telnet
access.
I'm familiar with all those, but making PCBoard talk telnet is the missing link. What do you use for that?
I solved the problem by running OS/2 WARP as a guest operating system under VMware's VM workstation product. I've got OS/2 WARP 3 running PCBoard sitting on a Windows 2008 R2 server as a guest VM. I no
longer have to worry about hardware. I only support telnet access.
I'm familiar with all those, but making PCBoard talk telnet is the
missing link. What do you use for that?
@MSGID: 2:362/6 0017cd66
I solved the problem by running OS/2 WARP as a guest operating
system under VMware's VM workstation product. I've got OS/2 WARP
3 running PCBoard sitting on a Windows 2008 R2 server as a guest
VM. I no longer have to worry about hardware. I only support
telnet access.
I'm familiar with all those, but making PCBoard talk telnet is the JK>missing link. What do you use for that?
Jeff
Democrats -- The party that penalizes success and rewards failure
Democrats -- The party that penalizes success and rewards failure
I don't like seeing political propaganda in a technical echo, taglines notwithstanding.
You may as well say democrats are lazy and stupid. Suppose I say
republicans are greedy and selfish. How does that help anyone?
Jeff
Democrats -- The party that penalizes success and rewards failure
I don't like seeing political propaganda in a technical echo,
taglines notwithstanding.
Democrats -- The party that penalizes success and rewards failure
I don't like seeing political propaganda in a technical echo,
taglines notwithstanding.
You may as well say democrats are lazy and stupid.
Suppose I say republicans are greedy and selfish.
How does that help anyone?
Democrats -- The party that penalizes success and rewards failure
I don't like seeing political propaganda in a technical echo,
taglines notwithstanding.
I typically only respond in political echoes and didn't turn off
taglines when I responded here. I'll turn it off in the future.
(Look no tagline below)
I don't like seeing political propaganda
I typically only respond in political echoes and didn't turn off taglines when I responded here. I'll turn it off in the future.
making PCBoard talk telnet is the missing link.
on OS/2, that would be the vmodem driver with the SIO replacement
comms package from Ray Gwinn of X00 fame...
making PCBoard talk telnet is the missing link.
on OS/2, that would be the vmodem driver with the SIO replacement
comms package from Ray Gwinn of X00 fame...
In the sio2k docs, Ray says Warp server ebiz fails when using
serial ports and IRQ 3. I also read that the server and client
code base was merged as of fixpak 13.
So I installed Warp 4, fixpak 9, and sio2k. I use a 2 port serial
PCI card on IRQ 3. I can start a file transfer but it stalls and
dies. So much for sio2k.
I hadn't looked at OS/2 since the early 1990s, and I was hoping it
had improved with age. But it's as frustrating now as it was then.
I don't like seeing political propaganda
I typically only respond in political echoes and didn't turn off
taglines when I responded here. I'll turn it off in the future.
I'm not strictly opposed to things off topic here, it's practically a TM>ghost town. I only know two PCBOARD systems active, worldwide, Mike TM>Luko's and Luis Silva's.
making PCBoard talk telnet is the missing link.
on OS/2, that would be the vmodem driver with the SIO replacement
comms package from Ray Gwinn of X00 fame...
In the sio2k docs, Ray says Warp server ebiz fails when using serial JK>ports and IRQ 3. I also read that the server and client code base
was merged as of fixpak 13.
So I installed Warp 4, fixpak 9, and sio2k. I use a 2 port serial
PCI card on IRQ 3. I can start a file transfer but it stalls and
dies. So much for sio2k.
Then I read that MCP2 has new serial drivers from IBM that support
PCI serial cards with IRQ sharing. So I tried MCP 2. Also stalls and JK>dies. Must be true about the problem with IRQ 3. And the MCP2 peer JK>networking fails when you disconnect a share and try to reconnect it.
At least that worked right on WARP 4.
There are some post MCP2 fixpaks, but google turns up no download
sites for them. Apparently the only way to get them is from the ECS JK>website, and for that you must be a paying customer.
I hadn't looked at OS/2 since the early 1990s, and I was hoping it
had improved with age. But it's as frustrating now as it was then.
I only know two PCBOARD systems active, worldwide
Well now we can say there are 3 PCBoard systems :)
I am running Warp 3 Connect, under VMworkstation with SIO. It took
me the better part of 8 hours to get OS/2 to load and run under VMworkstation but now it is solid. It means I never have to worry
about hardware again.
Right now I have a Windows 2008R2 server as the host OS running
instances of OS/2, Windows 2003R2 server, Linux Slackware 14.0,
Windows 7, a Juniper SSL VPN appliance VM and more.
i had to jump from Warp 3 Connect to eCS... i couldn't get Warp 4 of
any flavor to install and work on my machines... i didn't have time
to stay down longer than i was... several days was already too
long... so i went with eCS and haven't looked back... all of my
operation remaing the same as it was on Warp 3 Connect ;)
I'm not strictly opposed to things off topic here, it's practically
a ghost town. I only know two PCBOARD systems active, worldwide,
Mike Luko's and Luis Silva's. There's not much audience to offend;
the echo went unmoderated for a long time without trouble.
So I installed Warp 4, fixpak 9, and sio2k. I use a 2 port serial
PCI card on IRQ 3. I can start a file transfer but it stalls and
dies. So much for sio2k.
I only know two PCBOARD systems active, worldwide
It seems to me that you must have missed other PCBoard BBS's also since you have missed my BBS.
Please do a full study before you start counting next time.
So much for sio2k.
Did you ever think of disabling the serial port using IRQ 3 in the
BIOS and let SIO handle the port?
Did you ever think of disabling the serial port using IRQ 3 in the
BIOS and let SIO handle the port?
How can SIO handle the port without an IRQ? Use polling? I don't think
SIO will do that.
How can SIO handle the port without an IRQ? Use polling? I don't
think SIO will do that.
Well now we can say there are 3 PCBoard systems :)
Depends on your definition of "active".
Has it been in daily operation for a year or more, does it have any
non sysop users who actually call, etc.
Did you ever think of disabling the serial port using IRQ 3 in
the BIOS and let SIO handle the port?
How can SIO handle the port without an IRQ? Use polling? I don't
think SIO will do that.
It will; however, IIRC only if native OS/2 comm apps are using the
port. Otherwise, you have to assign IRQs for DOS and Win64 comm
apps.
My BSS has been around for around 20 years. I have a handful of users that remain.
How can SIO handle the port without an IRQ? Use polling?
It will; however, IIRC only if native OS/2 comm apps are using the
port. Otherwise, you have to assign IRQs for DOS and Win64 comm
i had to jump from Warp 3 Connect to eCS... i couldn't get Warp 4 of
any flavor to install and work on my machines... i didn't have time
to stay down longer than i was... several days was already too
long... so i went with eCS and haven't looked back... all of my
operation remaing the same as it was on Warp 3 Connect ;)
I couldn't install Warp 4 on real hardware until I got the idedasd
fixes for large hard drives. I wonder if that works with Warp 3
too. Is that why you had to upgrade from Warp 3?
I don't think I want to pay for ECS. Seems like their business is
on life support now, judging by their web site. Development plans
extend thru 2005 (or so)? That was almost a decade ago.
How can SIO handle the port without an IRQ? Use polling? I don't think
SIO will do that.
It will; however, IIRC only if native OS/2 comm apps are using the
port. Otherwise, you have to assign IRQs for DOS and Win64 comm
apps.
@MSGID: 1:266/512@fidonet.org e859e5cb
My BSS has been around for around 20 years. I have a handful of
users that remain.
OK. What's the telnet address?
I don't think I want to pay for ECS
I think Holger assumed that my IRQ 3 was a motherboard com port that JK>could be disabled in the BIOS. That's not so; it's a PCI expansion
card that PCI assigns to IRQ 3, because there is no COM2 on the JK>motherboard.
Here's my SIO config for using with PCBoard:
device=c:\sio\sio.sys [5,INTERNET:1F8,NONE:7] [6,INTERNET:1E8,NONE:7] [7,INTERNET:100,NONE:7] [8,INTERNET:108,NONE:7]
I don't use the first 4 comm ports and IRQ 7 is shared.
@MSGID: 2:362/6 0017b3a2
Here's my SIO config for using with PCBoard:
Thanks.
device=c:\sio\sio.sys [5,INTERNET:1F8,NONE:7]
[6,INTERNET:1E8,NONE:7] [7,INTERNET:100,NONE:7]
[8,INTERNET:108,NONE:7]
I don't use the first 4 comm ports and IRQ 7 is shared.
Are your PCBoard ports configured for FOSSIL, or COM port? I could
not tell from the SIO 1.60d docs if the VX00 FOSSIL works with
vmodem, or if you have to use COM ports for FOSSIL.
I still do assume that the BIOS for your MoBo assigns COM ! and COM 2
as available options. Disable them in the BIOS!
Are your PCBoard ports configured for FOSSIL, or COM port? I
could not tell from the SIO 1.60d docs if the VX00 FOSSIL works
with vmodem, or if you have to use COM ports for FOSSIL.
if the VX00 FOSSIL works with vmodem
if i am reading your question correctly, yes, it absolutely does... everything i use here that is accessible via telnet has to go thru
VX00
and i have several external door type programs that do not have
fossil capability... AFAIK, everything works
I installed Warp 4, fixpak 9, and sio2k. I use a 2 port serial
PCI card on IRQ 3. I can start a file transfer but it stalls and
dies. So much for sio2k.
use the previous version instead of sio2k
Ray says Warp server ebiz fails when using serial ports and IRQ
3. I also read that the server and client code base was merged
as of fixpak 13.
But I do know this: not all BIOS have a COM2 enable/disable option
when the hardware port does not exist on the motherboard.
if the VX00 FOSSIL works with vmodem
if i am reading your question correctly, yes, it absolutely does... everything i use here that is accessible via telnet has to go thru
VX00
I understand telnet would require vmodem. But whether or not VX00
is used seems like a different question ...
JOHN KELLY wrote to HOLGER GRANHOLM <=-
Did you ever think of disabling the serial port using IRQ 3 in the
BIOS and let SIO handle the port?
How can SIO handle the port without an IRQ? Use polling? I don't think
SIO will do that.
JOHN KELLY wrote to JEFF BINKLEY <
Are your PCBoard ports configured for FOSSIL, or COM port? I could not tell from the SIO 1.60d docs if the VX00 FOSSIL works with vmodem, or
if you have to use COM ports for FOSSIL.
Sysop: | Angel Ripoll |
---|---|
Location: | Madrid, Spain |
Users: | 17 |
Nodes: | 4 (0 / 4) |
Uptime: | 17:36:39 |
Calls: | 563 |
Files: | 81,769 |
Messages: | 1,201,217 |