¯ ®
¯ BarryMartin3@ ®
¯ @MyMetronet.NET ®
¯ ®
¯ (Humans know what ®
¯ to remove.) ®
.. Be an iconoclast. Stay with DOS.
--- MultiMail/Win32 v0.47
þ wcECHO 4.2 ÷ ILink: The Safe BBS þ Bettendorf, IA
BARRY MARTIN wrote:
¯ ®
¯ BarryMartin3@ ®
¯ @MyMetronet.NET ®
¯ ®
¯ (Humans know what ®
¯ to remove.) ®
.. Be an iconoclast. Stay with DOS.
This was a minimalist message? :)
Hi Ky!
> .. Be an iconoclast. Stay with DOS.
I guess! Sort of a reaction to Lee saying we yakked to much! <JOKE!!!>
Anyway, referenced an article on using the Raspberry Pi to emulate
MS-DOS and optionally as a couple of early Windows versions:
https://magpi.raspberrypi.org/articles/build-a-dos-emulation-system?mc_c id=7589d7823d&mc_eid=b112add5d7
> .. Be an iconoclast. Stay with DOS.
Oh, I see. The message is up above!
KM> This was a minimalist message? :)
I guess! Sort of a reaction to Lee saying we yakked to much! <JOKE!!!>
He's gonna have a long wait for us to shut up <g>
Anyway, referenced an article on using the Raspberry Pi to emulate
MS-DOS and optionally as a couple of early Windows versions: https://magpi.raspberrypi.org/articles/build-a-dos-emulation-system?mc_c id=7589d7823d&mc_eid=b112add5d7
Ooh, neat! Never thought of running Win3.1 on a Pi, but now that
I think of it... Win3.1 just needs DOS to run, so DOSBox should
work to host it.
Hi Ky!
> > .. Be an iconoclast. Stay with DOS.
KM> Oh, I see. The message is up above!
KM> KM> This was a minimalist message? :)
> I guess! Sort of a reaction to Lee saying we yakked to much! <JOKE!!!>
KM> He's gonna have a long wait for us to shut up <g>
<logging in> ..."No such user" ??!!
> Anyway, referenced an article on using the Raspberry Pi to emulate
> MS-DOS and optionally as a couple of early Windows versions:
> https://magpi.raspberrypi.org/articles/build-a-dos-emulation-system?mc_c
> id=7589d7823d&mc_eid=b112add5d7
KM> Ooh, neat! Never thought of running Win3.1 on a Pi, but now that
KM> I think of it... Win3.1 just needs DOS to run, so DOSBox should
KM> work to host it.
So I guess it is easier to understand the information when the
information is present! <g> Back in the old days I had a Windows and if
I started DOS then opened Windows it worked fine but if I configured it
to start at Windows and shell to DOS would in short time lock up. Had
others check and they didn't find a problem with the hardware nor
software. (Guess that was the start of my annoyance with Windows.)
As far as running Windows on an RPi, I think the article suggested a Raspberry Pi 4 -- faster than the earlier versions so a plus there.
I'd probably go with the 8 GB version over the 4 -- for this application saving a few dollars on the less expensive option isn't worth it. OTOH
one of the nice things about the Pi's is one can remove the SD card,
insert another and it's a 'different' computer! Easy to see if one
likes something, is fine with the response or an upgrade is worthwhile.
Back in the old days I had a Windows and if
I started DOS then opened Windows it worked fine but if I configured it
to start at Windows and shell to DOS would in short time lock up. Had others check and they didn't find a problem with the hardware nor
software. (Guess that was the start of my annoyance with Windows.)
Huh. That's very strange, but I'd guess when it went direct to
Windows, the underlying DOS memory manager was not getting loaded correctly. Or the config options were different; as I vaguely
recall Win3.1 used different config options for its DOS shell.
I recall having some rather strange config.sys and autoexec.bat
bits to deal with something like this, then again I was using
DRDOS underneath, and while it had more functions, it also had
more cranks compared to MSDOS.
As far as running Windows on an RPi, I think the article suggested a Raspberry Pi 4 -- faster than the earlier versions so a plus there.
I'd probably go with the 8 GB version over the 4 -- for this application saving a few dollars on the less expensive option isn't worth it. OTOH
one of the nice things about the Pi's is one can remove the SD card,
insert another and it's a 'different' computer! Easy to see if one
likes something, is fine with the response or an upgrade is worthwhile.
Yeah, that way you're also flexible for other projects.
Hi Ky!
> Back in the old days I had a Windows and if
> I started DOS then opened Windows it worked fine but if I configured it
> to start at Windows and shell to DOS would in short time lock up. Had
> others check and they didn't find a problem with the hardware nor
> software. (Guess that was the start of my annoyance with Windows.)
KM> Huh. That's very strange, but I'd guess when it went direct to
KM> Windows, the underlying DOS memory manager was not getting loaded
KM> correctly. Or the config options were different; as I vaguely
KM> recall Win3.1 used different config options for its DOS shell.
Something like that. I did have at least one person take a look and everything appeared correct. Oh well, just loaded DOS first, then
Windows when I needed it.
KM> I recall having some rather strange config.sys and autoexec.bat
KM> bits to deal with something like this, then again I was using
KM> DRDOS underneath, and while it had more functions, it also had
KM> more cranks compared to MSDOS.
The 'we have good news and we have bad news' thing. I think I had tried DRDOS but decided it would be best for me to stick with the 'mainstream' stuff packed with the computers we were selling at the store and I could
(and did) provide some customer support.
> As far as running Windows on an RPi, I think the article suggested a
> Raspberry Pi 4 -- faster than the earlier versions so a plus there.
> I'd probably go with the 8 GB version over the 4 -- for this application
KM> Yeah, that way you're also flexible for other projects.
Plus relatively easy to have a back up: the newer OS allow copying of
the entire SD card as opposed to just the data partition (maybe was also
part of the OS partiion, I don't recall). Having a clone of the card is nice!
If I had to bet, I'd be looking at the FILES= statement in CONFIG.SYS --
due to some cranks left over from the MSDOS4.x era, some programs, and therefore Win3.1x itself, needed them set to some ridiculously high
number. I remember this specifically because DRDOS Did Things
Differently there, and MSOffice 4.0 would not run, and Windows was a
little goofy in some other way I've forgotten. So I called Microsoft,
and was told to set FILES and HANDLES to some absurdly high numbers...
and then suddenly all was well. (And Windows never, ever crashed again,
nor even misbehaved in any noteworthy way. Seven years without a single crash!)
If I had to bet, I'd be looking at the FILES= statement in CONFIG.SYS --
due to some cranks left over from the MSDOS4.x era, some programs, and
therefore Win3.1x itself, needed them set to some ridiculously high
number. I remember this specifically because DRDOS Did Things
Differently there, and MSOffice 4.0 would not run, and Windows was a
little goofy in some other way I've forgotten. So I called Microsoft,
and was told to set FILES and HANDLES to some absurdly high numbers...
and then suddenly all was well. (And Windows never, ever crashed again,
nor even misbehaved in any noteworthy way. Seven years without a single
crash!)
I can remember setting FILES to no lower than 50, and sometimes as high as 70, to get things to work right. You may be onto something there.
> Back in the old days I had a Windows and if
> I started DOS then opened Windows it worked fine but if I configured it
> to start at Windows and shell to DOS would in short time lock up. Had
> others check and they didn't find a problem with the hardware nor
> software. (Guess that was the start of my annoyance with Windows.)
KM> Huh. That's very strange, but I'd guess when it went direct to
KM> Windows, the underlying DOS memory manager was not getting loaded
KM> correctly. Or the config options were different; as I vaguely
KM> recall Win3.1 used different config options for its DOS shell. Something like that. I did have at least one person take a look and everything appeared correct. Oh well, just loaded DOS first, then
Windows when I needed it.
If I had to bet, I'd be looking at the FILES= statement in
CONFIG.SYS -- due to some cranks left over from the MSDOS4.x era,
some programs, and therefore Win3.1x itself, needed them set to
some ridiculously high number.
I remember this specifically
because DRDOS Did Things Differently there, and MSOffice 4.0
would not run, and Windows was a little goofy in some other way
I've forgotten. So I called Microsoft, and was told to set FILES
and HANDLES to some absurdly high numbers... and then suddenly
all was well. (And Windows never, ever crashed again, nor even
misbehaved in any noteworthy way. Seven years without a single
crash!)
You may note a common theme here... the problem was that DOS4.x
didn't close files properly on disk, and apparently these
programs compensated, which was disagreeable to other DOS
versions (and thereby caused the very files-left-open problem it
was supposed to prevent).
KM> I recall having some rather strange config.sys and autoexec.bat
KM> bits to deal with something like this, then again I was using
KM> DRDOS underneath, and while it had more functions, it also had
KM> more cranks compared to MSDOS.
The 'we have good news and we have bad news' thing. I think I had tried DRDOS but decided it would be best for me to stick with the 'mainstream' stuff packed with the computers we were selling at the store and I could (and did) provide some customer support.
Yeah, I wound up using it because the person who got me started
on this stuff was a DRDOS enthusiast, but fact was it wasn't
worth the trouble, with rare exceptions -- frex, you could
multiboot different species of DOS... tho what it actually did
was shell to the next DOS, not a true multiboot. (At one point I
had a very silly setup of three different DOSs on the same
system, that chain-booted to the one you wanted.)
DRDOS had a DPMI memory manager, which was great for Windows, but
caused conflicts with stuff like DOOM that had its own DPMI
manager... so needed a boot option to set up memory differently
for that.
And DRDOS's performance was (per actual test) 20% slower than
MSDOS6. So after the Win3.1 system with DRDOS7 was finally
retired, I never messed with it again., Nowadays when I use DOS,
by preference it's MSDOS7 from Win98 (with the 8.0 mouse driver).
Best performance and as bug-free as anything gets. FreeDOS is
okay but I seem to run into more holes and stuff that doesn't
work as expected.
Geez, look what happens when you stir the ancient sludge in the
sewers of Ky's brain...
Hi Ky!
KM> If I had to bet, I'd be looking at the FILES= statement in
KM> CONFIG.SYS -- due to some cranks left over from the MSDOS4.x era,
KM> some programs, and therefore Win3.1x itself, needed them set to
KM> some ridiculously high number.
That would almost make sense: here it seemed as if a buffer/holding area
of some sort was being overloaded/overfilled as always worked for a
little while and then stopped. The amount of time varied: sometimes
almost immediately to a few minutes. Would be nice to be able to go
back and check.
KM> all was well. (And Windows never, ever crashed again, nor even
KM> misbehaved in any noteworthy way. Seven years without a single
KM> crash!)
Seven days is considered a long time!!
KM> You may note a common theme here... the problem was that DOS4.x
KM> didn't close files properly on disk, and apparently these
KM> programs compensated, which was disagreeable to other DOS
KM> versions (and thereby caused the very files-left-open problem it
KM> was supposed to prevent).
One fix for a problem creates a problem which needs to be fixed
elsewhere. Which sort of makes points for having a base operating
system and seperate applications/utilites as opposed to having those applications and utilities built into the OS. Seems like separate and independent would be easier to correct without screwing up something
else. (Still a possibilty, just less so.)
KM> Yeah, I wound up using it because the person who got me started
KM> on this stuff was a DRDOS enthusiast, but fact was it wasn't
Something like when I got started with Linux. The utility I was using
at the time for recording TV was MythDora, which is based on Fedora.
..Hmm: so why did I go Ubuntu instead of Fedora??
KM> retired, I never messed with it again., Nowadays when I use DOS,
KM> by preference it's MSDOS7 from Win98 (with the 8.0 mouse driver).
I'll admit to not really needing to return to the Old Stuff, mainly
because nothing I'm using needs it, though some does use NonCurrent
Stuff! Glad I learned the more or less bare bones MS-DOS and early
Windows: great for troubleshooting as I sort of understand what is
happening.
KM> Geez, look what happens when you stir the ancient sludge in the
KM> sewers of Ky's brain...
So there was this article about how the Thames River was London's sewer
and during droughts..... <g>
KM> If I had to bet, I'd be looking at the FILES= statement in
KM> CONFIG.SYS -- due to some cranks left over from the MSDOS4.x era,
KM> some programs, and therefore Win3.1x itself, needed them set to
KM> some ridiculously high number.
That would almost make sense: here it seemed as if a buffer/holding area
of some sort was being overloaded/overfilled as always worked for a
little while and then stopped. The amount of time varied: sometimes
When it ran out of file handles, probably. Windows could scrape
by on 20 (IIRC) but as soon as you run something else...
kablooie.
almost immediately to a few minutes. Would be nice to be able to go
back and check.
Time machine needs rebooting? :D
KM> all was well. (And Windows never, ever crashed again, nor even
KM> misbehaved in any noteworthy way. Seven years without a single
KM> crash!)
Seven days is considered a long time!!
Not in MY house! <g>
KM> You may note a common theme here... the problem was that DOS4.x
KM> didn't close files properly on disk, and apparently these
KM> programs compensated, which was disagreeable to other DOS
KM> versions (and thereby caused the very files-left-open problem it
KM> was supposed to prevent).
One fix for a problem creates a problem which needs to be fixed
Haha, so it goes!
elsewhere. Which sort of makes points for having a base operating
system and separate applications/utilites as opposed to having those applications and utilities built into the OS. Seems like separate and independent would be easier to correct without screwing up something
else. (Still a possibilty, just less so.)
Or why I'm a big fan of portable apps, and why we have Flatpak
and AppImage for linux (given DLL Hell has NOTHING on Dependency
Hell).
KM> Yeah, I wound up using it because the person who got me started
KM> on this stuff was a DRDOS enthusiast, but fact was it wasn't
Something like when I got started with Linux. The utility I was using
at the time for recording TV was MythDora, which is based on Fedora.
..Hmm: so why did I go Ubuntu instead of Fedora??
There's no excuse for Ubuntu. <g>
Seriously, it makes Win10 seem agreeable...
KM> retired, I never messed with it again., Nowadays when I use DOS,
KM> by preference it's MSDOS7 from Win98 (with the 8.0 mouse driver).
I'll admit to not really needing to return to the Old Stuff, mainly
because nothing I'm using needs it, though some does use NonCurrent
Yeah, I'm down to just a couple things that need Old Stuff, and
some year I'll find me a Pascal programmer and get the 16bit DOS
pedigree program converted to 32bit Windows. Or x64 linux, as the
case may be.
Stuff! Glad I learned the more or less bare bones MS-DOS and early
Windows: great for troubleshooting as I sort of understand what is happening.
Indeed... I can feel baffled often enough without lacking these
old foundations!
KM> Geez, look what happens when you stir the ancient sludge in the
KM> sewers of Ky's brain...
So there was this article about how the Thames River was London's sewer
and during droughts..... <g>
....they found Ubuntu CDs?? :D
Hi Ky!
> That would almost make sense: here it seemed as if a buffer/holding area
> of some sort was being overloaded/overfilled as always worked for a
> little while and then stopped. The amount of time varied: sometimes
KM> When it ran out of file handles, probably. Windows could scrape
KM> by on 20 (IIRC) but as soon as you run something else...
KM> kablooie.
Probably -- not questioning, just not recalling as that was a long time
ago, and haven't fiddled with this Windows XP (on the virtual machine)
in I don't know how long -- I think it's even a clone of what was on the
old computer. ...Yup: 2008 (!) Well, c:\windows\system32\config.nt has Files=40. (And I've switched topic from ~WFWG to XP.)
> almost immediately to a few minutes. Would be nice to be able to go
> back and check.
KM> Time machine needs rebooting? :D
Might be abad time to find the motherboard battery is dead and we're at
the computer epoch date!
> KM> all was well. (And Windows never, ever crashed again, nor even
> KM> misbehaved in any noteworthy way. Seven years without a single
> KM> crash!)
> Seven days is considered a long time!!
KM> Not in MY house! <g>
It's all due to the typewriter hung onthe fence!!
> One fix for a problem creates a problem which needs to be fixed
KM> Haha, so it goes!
Job security for the programmers! Fix on problem, create another, but
not so it looks like incompetence!
KM> Or why I'm a big fan of portable apps, and why we have Flatpak
KM> and AppImage for linux (given DLL Hell has NOTHING on Dependency
KM> Hell).
I can sort of see both sides: mainly why re-invent the wheel so use
something already working (guess called a 'dependency'), but of course
that has backfired with the utility no longer working when the other
utility was altered. (Thinking in particular of GET and STRINGS.)
> KM> Yeah, I wound up using it because the person who got me started
> KM> on this stuff was a DRDOS enthusiast, but fact was it wasn't
> Something like when I got started with Linux. The utility I was using
> at the time for recording TV was MythDora, which is based on Fedora.
> ..Hmm: so why did I go Ubuntu instead of Fedora??
KM> There's no excuse for Ubuntu. <g>
Maybe the Desktop background caught my eye: a Felt Fedora - yawn! An Energetic Ermine -- hmm! <g> ...Probably more MythDora died (no longer supported) and Mythbuntu was the replacement. (I do recall looking at
other options but they appeared to be too complex, especially for the
other person here.) Mythbuntu was built on Ubuntu and so if seems
halfway logical to get more into Ubuntu.
KM> Seriously, it makes Win10 seem agreeable...
I'm thinking it's just a personality conflict: no real problems here;
have been some minor issues but IMO they got resolved quickly. Now
maybe when looking at a more in-depth and technical mindset....
https://www.howtoforge.com/tutorial/run-dos-application-in-linux/
He's wanting to run a 16-bit MS-DOS game. WINE won't work because
16-bit applications want to access the first 64K of kernel memory and
that's a security issue. DOSBox and DOSemu seem to be working.
I was expecting another page as he said 'tutorial'...
This article may give you some other clues: https://stackoverflow.com/questions/15597155/porting-16-bit-dos-x86-asse mbly-to-32-bit-linux-x86-assembly
My search was "convert 16 bit DOS to Linux" ==> https://www.google.com/search?channel=fs&client=ubuntu&q=convert+16+bit+ DOS+to+Linux
Probably the more technical hits will be what you need -- they're over
my head.
<chuckle> Yeah! Like my little issue with getting the fiber optic
system going here: details is posts with Nancy in Chit Chat, basically I figured out why my computers weren't seeing the outside world: (a)
Ethernet cable was disconnected, and (b) needed another device (a router
-- I wasn't sure of the terminology so when talking to IT let them give
me their name for the device).
Over the years have done lots of troubleshooting by paying attention to details. Stuff doesn't run off 'magic'.
> KM> Geez, look what happens when you stir the ancient sludge in the
> KM> sewers of Ky's brain...
> So there was this article about how the Thames River was London's sewer
> and during droughts..... <g>
KM> ....they found Ubuntu CDs?? :D
Nah: Prodigy!
.. Shell to DOS...Come in DOS; do you Copy? Shell to DOS...
> That would almost make sense: here it seemed as if a buffer/holding area
> of some sort was being overloaded/overfilled as always worked for a
> little while and then stopped. The amount of time varied: sometimes
KM> When it ran out of file handles, probably. Windows could scrape
KM> by on 20 (IIRC) but as soon as you run something else...
KM> kablooie.
Probably -- not questioning, just not recalling as that was a long time
I probably wouldn't remember so specifically except for that
MSOffice problem, and that my brain never throws away anything.
Doesn't label or index a durn thing, but keeps all of it!
ago, and haven't fiddled with this Windows XP (on the virtual machine)
in I don't know how long -- I think it's even a clone of what was on the
old computer. ...Yup: 2008 (!) Well, c:\windows\system32\config.nt has Files=40. (And I've switched topic from ~WFWG to XP.)
Topic? What topic?? :D Tho I vaguely recall that with the NT
base, it no longer really matters, tho might be there for
compatibility.
> almost immediately to a few minutes. Would be nice to be able to go
> back and check.
KM> Time machine needs rebooting? :D
Might be a bad time to find the motherboard battery is dead and we're at
the computer epoch date!
Especially if it's Borg (the first of mine built by assimilating
other PCs), who left to its own devices thought the year was
2093!!
> KM> all was well. (And Windows never, ever crashed again, nor even
> KM> misbehaved in any noteworthy way. Seven years without a single
> KM> crash!)
> Seven days is considered a long time!!
KM> Not in MY house! <g>
It's all due to the typewriter hung onthe fence!!
38 years or so later, the warning is still in force! <g>
> One fix for a problem creates a problem which needs to be fixed
KM> Haha, so it goes!
Job security for the programmers! Fix on problem, create another, but
not so it looks like incompetence!
I've heard of some actually attempting that... thing is, those
who think that way usually aren't as good as they thought... and
get caught.
KM> Or why I'm a big fan of portable apps, and why we have Flatpak
KM> and AppImage for linux (given DLL Hell has NOTHING on Dependency
KM> Hell).
I can sort of see both sides: mainly why re-invent the wheel so use something already working (guess called a 'dependency'), but of course
Dependency: same as a DLL, except for linux. Shared bits of
programs and/or OS.
But the problem is that dependencies can get out of sync, and
then whichever program didn't update its build... no longer
works.
In fact I lost my preferred font manager to that very problem. It
has a dependency old enough it conflicts with current OS
versions. So this program works on the, uh, archival PCLOS that
I've never updated, but not on the one I keep up to date.
(Synaptic removed it, being fairly good about resolving conflicts
that way. Otherwise I would have had several broken packages.)
> KM> Yeah, I wound up using it because the person who got me started
> KM> on this stuff was a DRDOS enthusiast, but fact was it wasn't
> Something like when I got started with Linux. The utility I was using
> at the time for recording TV was MythDora, which is based on Fedora.
> ..Hmm: so why did I go Ubuntu instead of Fedora??
KM> There's no excuse for Ubuntu. <g>
Maybe the Desktop background caught my eye: a Felt Fedora - yawn! An Energetic Ermine -- hmm! <g> ...Probably more MythDora died (no longer supported) and Mythbuntu was the replacement. (I do recall looking at
That sounds like a less fanciful explanation. <g>
other options but they appeared to be too complex, especially for the
other person here.) Mythbuntu was built on Ubuntu and so if seems
halfway logical to get more into Ubuntu.
Whereas I have a variety of OSs... in fact Fireball has
accumulated a stack of <counts> SIX hard drives with several
different Windows and one PCLOS. (I no longer multiboot, thanks
to issues variously with GRUB and with the current Windows
bootloader. Much safer to just swap HDs.)
KM> Seriously, it makes Win10 seem agreeable...
I'm thinking it's just a personality conflict: no real problems here;
Heh.. in my book, Gnome3 is completely unusable. If I wanted a
cellphone interface, I'd use a bloody cellphone!!
Also, compared to just about every other species of linux (except
possibly Mageia), Ubuntu is a hog. Not so critical on newish
hardware, but it's downright sluggish on an older box. Realized
why when I compared it directly to Mint... Mint is built from
Ubuntu, but runs MUCH faster, and... per actual count only loads
1/4th as many modules. Well, no wonder!!
So that's how I came to so very much dislike Ubuntu.
have been some minor issues but IMO they got resolved quickly. Now
maybe when looking at a more in-depth and technical mindset....
Or a complete lack of patience :)
https://www.howtoforge.com/tutorial/run-dos-application-in-linux/
He's wanting to run a 16-bit MS-DOS game. WINE won't work because
16-bit applications want to access the first 64K of kernel memory and
that's a security issue. DOSBox and DOSemu seem to be working.
Decided WINE and DOSbox both not worth the effort; easier to run VirtualBox and WinXP. In fact that is now how I deal with 16-bit
anything, and with Win-only apps I can't live without. And being
lazy, built it once then exported an OVA, so I have the same
WinXP in every VM.
This article may give you some other clues: https://stackoverflow.com/questions/15597155/porting-16-bit-dos-x86-asse mbly-to-32-bit-linux-x86-assembly
Assembly language is its own arcanity... this program is in
Pascal (author gave me the source code for my personal use... if
I could track him down again I'd ask about opensourcing it).
My search was "convert 16 bit DOS to Linux" ==> https://www.google.com/search?channel=fs&client=ubuntu&q=convert+16+bit+ DOS+to+Linux
Now my brain hurts. <g>
Probably the more technical hits will be what you need -- they're over
my head.
That's because they're hitting me over the head! <g>
<chuckle> Yeah! Like my little issue with getting the fiber optic
system going here: details in posts with Nancy in Chit Chat, basically I figured out why my computers weren't seeing the outside world: (a)
Ethernet cable was disconnected, and (b) needed another device (a router
-- I wasn't sure of the terminology so when talking to IT let them give
me their name for the device).
Ah, yes, the old "unplugged cable" gambit... <g>
Over the years have done lots of troubleshooting by paying attention to details. Stuff doesn't run off 'magic'.
Wait, it doesn't??
> KM> Geez, look what happens when you stir the ancient sludge in the
> KM> sewers of Ky's brain...
> So there was this article about how the Thames River was London's sewer
> and during droughts..... <g>
KM> ....they found Ubuntu CDs?? :D
Nah: Prodigy!
LOL, not AOL? :)
.. Shell to DOS...Come in DOS; do you Copy? Shell to DOS...
I hear water...
| Sysop: | Martin J Mitchell |
|---|---|
| Location: | Scotland |
| Users: | 5 |
| Nodes: | 10 (0 / 10) |
| Uptime: | 109:18:00 |
| Calls: | 127 |
| Files: | 29,254 |
| Messages: | 54,760 |