I've been running Max under DOS and Windows 95/98 since v1 -- but now I've taken the big step to XP!! I'm still running the DOS version of Max, but I'm wondering if I should take the plunge and change to the w32 version?
Could someone point me at the pluses and minuses of such a change, please?
I've been running Max under DOS and Windows 95/98 since v1 -- but now I've taken the big step to XP!! I'm still running the DOS version of Max, but I'm wondering if I should take the plunge and change to the w32 version?
Could someone point me at the pluses and minuses of such a change, please?
Heh heh, I am of the mind that if it ain't broken, don't fix it :)
Heh heh, I am of the mind that if it ain't broken, don't fix
it :)
I don't disagree -- but I notice the cpu load with a
binkley and 2 max telnets is a solid 100%!!! I'm sort of
hoping that changing to the w32 version would reduce that?
That is true. CPU utilisation for DOS programs in multitasking OS's
like Windows depend on whether the program releases time slices to
the OS.
Maximus DOS doesn't do time slicing, and therefore kills the CPU.
BinkleyTerm DOS 2.60 (?) does handle time slicing, so does not hog
CPU.
Maximus/32 is faster than the DOS version of Maximus. E[...]g.
use WinFOSSIL or Netserial.
I allow all 16 telnet DOS nodes to be spawned on a single PC and
let performance be the caller's problem. Heh. Besides, these days
having even 2 genuine simultaneous callers online is wishful
thinking.
I recommend running Maximus in VMware DOS under Windows XP.
I don't disagree -- but I notice the cpu load with a
binkley and 2 max telnets is a solid 100%!!! I'm sort of
hoping that changing to the w32 version would reduce that?
That is true. CPU utilisation for DOS programs in multitasking OS's
like Windows depend on whether the program releases time slices to
the OS.
I run WFC mode using Maximus/32 specifically for scheduling BBS maintenance events because it can idle all day without CPU
utilisation.
The disadvantage of Maximus/32 is its direct com port access
requirement. If you try to set up a Maximus/32 node on a physically non-existant com port, WFC will abort. Also anything that requires
a FOSSIL will not work in Maximus/32. And hot com port passing will
not work with Maximus/32 (ie. DTR is dropped when passing callers
between DOS programs eg. BinkleyTerm to/from Maximus) unless you
use WinFOSSIL or Netserial.
In my experience Maximus/32 without WinFOSSIL or Netserial is only
useful for local nodes.
I recommend running Maximus in VMware DOS under Windows
XP.
Hmm - I'll think on that one.
I sure like my MS-DOS box running Max/Squish/Binkley. I know it's a Dinosaur, but I like my pet Dinosaur. :)
I guess I'll have to go back to having a fake binkley as a
front end -- it worked under 98, so I guess I can make it
work under xp! :-)
I only use BT to browse the outbound queues, and do mail
maintenance events eg. Squish Out Squash, create poll files for
BinkD etc. 99.99% of the time it's just merely occupying taskbar &
memory space, which doesn't even look pretty.
I recommend running Maximus in VMware DOS under Windows
XP.
Hmm - I'll think on that one.
I sure like my MS-DOS box running Max/Squish/Binkley. I
know it's a Dinosaur, but I like my pet Dinosaur. :)
I'm planning some upgrading in the future here once other
business details are sorted out. THough the bbs is for
hobby activity related to emergency communications and ham
radio it will benefit from these upgrades by being able to
offer telnet access as well as pots. POts will always
remain with binkley as front end with max dos underneath,
but haven't sorted out all the issues yet. Your post brings
up some questions, and I'd like your input. Remember I'm
not a real programmer, just a radio op and audio guy who
runs a rather simple installation.
That is true. CPU utilisation for DOS programs in
multitasking OS's like Windows depend on whether the program
releases time slices to the OS.
NOt an issue for the pots system with binkleyterm and max
dos as it would be on a separate machine, sharing message
and file areas over the lan.
I run WFC mode using Maximus/32 specifically for scheduling
BBS maintenance events because it can idle all day without
CPU utilisation.
This would be advantageous as telnettable max would
probably be on machine with shared message and file areas.
The disadvantage of Maximus/32 is its direct com port
access requirement. If you try to set up a Maximus/32 node
on a physically non-existant com port, WFC will abort. Also
anything that requires a FOSSIL will not work in Maximus/32.
And hot com port passing will not work with Maximus/32 (ie.
DTR is dropped when passing callers between DOS programs eg.
BinkleyTerm to/from Maximus) unless you use WinFOSSIL or
Netserial.
That might make things interesting, as another machine will
be handling all outside connectivity through dsl. iF that's
workable then max32 might still be an option for me, as I
run no doors at this time. Hence we wouldn't need a fossil
driver nor com port sharing.
Trying to get a grasp of the issues I'm going to face
before I end up fishing around in the dark. I"m an old dos
dinosaur that doesn't do windows, but have one machine
running 98 that would be usable for this.
AS I said earlier, I don't run any door games, or anything
else in doorway mode at this time. sUggestions are most
welcome.
In my experience Maximus/32 without WinFOSSIL or Netserial
is only useful for local nodes.
I would like to hear if you think this is true in my
application as well.
I'm planning some upgrading in the future here once other
business details are sorted out. THough the bbs is for
hobby activity related to emergency communications and ham
radio it will benefit from these upgrades by being able to
offer telnet access as well as pots. POts will always
Man you mean you haven't hooked up NetFOSS or Netserial - what have
you been DOING.
I dunno. Imo using a BBS sounds inappropriate, probably because the
words "hobby" and "emergency" shouldn't be used close together in a sentence.
remain with binkley as front end with max dos underneath,
but haven't sorted out all the issues yet. Your post brings
up some questions, and I'd like your input. Remember I'm
You should have no problems with Maximus/32 if you avoid passing connections between separate DOS windows.
NOt an issue for the pots system with binkleyterm and max
dos as it would be on a separate machine, sharing message
and file areas over the lan.
Even if you have POTS on a separate PC, if you intend on setting up telnettable Maximus you will probably have to use the DOS version
of Maximus on Windows, at which point it will hog the CPU eg. 30% -
50% per active node.
This is because most free telnet servers (TelSrv, GameSrv, Net2BBS)
only run on Windows and require a TCP/IP FOSSIL emulator (eg.
NetFOSS) to connect to the BBS, and only the Maximus DOS binary
supports FOSSILs.
If you can afford USD$50 - USD$200 to register virtual
modems then there's no problem. (Or you can run the Maximus OS/2
with VMODEM or Linux binaries which are free options. But then you
will have to use OS/2 and/or Linux. Heh)).
That might make things interesting, as another machine will
be handling all outside connectivity through dsl. iF that's
workable then max32 might still be an option for me, as I
run no doors at this time. Hence we wouldn't need a fossil
driver nor com port sharing.
Yeah that will probably work. Atleast the Maximus multinode stuff
eg. online chat will still work between separate computers
regardless of connection type (dialup/DSL) because IPC is handling
the semaphorish exchange between nodes (if the PCs are networked).
Trying to get a grasp of the issues I'm going to face
before I end up fishing around in the dark. I"m an old dos
dinosaur that doesn't do windows, but have one machine
running 98 that would be usable for this.
Well, you can always use modern technology and substitute your
Maximus BBS for Linux services. Eg. run a PPP and/or TCP/IP
connected webserver, gopher, nntp server etc. There's Apache for
Windows and Linux et al. This way you will have no technological/software/redundancy problems.
And people can use their web browsers (!) And you can show pictures
and/or pornography (!) You can't get all that with a BBS. Plus
simple html files load fast even at 33.6 kbps.
AS I said earlier, I don't run any door games, or anything
else in doorway mode at this time. sUggestions are most
welcome.
If you don't require FOSSIL compatibility (usually for doors via
Xtern_* exits) or pass connections between seperate DOS windows,
then Maximus/32 will probably suffice.
When setting up telnettable Maximus you need to decide between
1) suffering CPU performance problems with Maximus/DOS or 2)
paying for virtual modems to use Maximus/32.
Else use the Maximus OS/2 or Linux binaries.
Man you mean you haven't hooked up NetFOSS or Netserial -
what have you been DOING.
Nope, not on a dial-up internet connection on one line.
VOlunteers is more the right word, I object to the "hobby"
designation myself. SHall we just say for volunteer
emergency communicators <g>.
I"ll give it some study then, see what happens, but looks
like i"ll be running the lnux executables ,g>.
True enough, but staying with plain text for most displays,
it's about the info, and it's about being able to connect
to it with just about anything. IF all you've got is an old
1200 baud modem it has a landline. No slow to load
graphics, no hassles with what plug-ins your browser has.
From your discussion above it sounds like the linux
executable is my way to go here. oR running the dos
executable on the 98 machine.
I think option 3 sounds like the way to go here <g>. Have
one linux box anyway that will be networked but have other
plans for it.
One day that network card will die and you won't find a
DOS/W3.x/OS2 compatible NIC replacement.
Man you mean you haven't hooked up NetFOSS or Netserial -
what have you been DOING.
Nope, not on a dial-up internet connection on one line.
It still would have worked. Heh.
VOlunteers is more the right word, I object to the "hobby"
designation myself. SHall we just say for volunteer
emergency communicators <g>.
That would be more sensible.
I'll give it some study then, see what happens, but looks
like i'll be running the lnux executables ,g>.
The problem with the Linux version of Maximus is that it's more
flakey, less tested and unsupported.
True enough, but staying with plain text for most displays,
it's about the info, and it's about being able to connect
to it with just about anything. IF all you've got is an old
1200 baud modem it has a landline. No slow to load
graphics, no hassles with what plug-ins your browser has.
You don't need plugins for HTML.
There's nothing a BBS can't display that can't be done with HTML.
In an emergency I personally would prefer point'n'click interfaces
when browsing for information instead of telnet.
Up to you.
I think option 3 sounds like the way to go here <g>. Have
one linux box anyway that will be networked but have other
plans for it.
Just dump everything on one box.
Thursday May 22 2008 07:39, Minh Van Le wrote to Kevin
Klement:
One day that network card will die and you won't find a
DOS/W3.x/OS2 compatible NIC replacement.
Nice!
Now you got me searching the www for a NE2000 NIC. :)
Sysop: | digital man |
---|---|
Location: | Riverside County, California |
Users: | 1,042 |
Nodes: | 15 (0 / 15) |
Uptime: | 144:12:02 |
Calls: | 500,263 |
Calls today: | 1 |
Files: | 95,201 |
D/L today: |
108 files (65,739K bytes) |
Messages: | 464,620 |