Bit of a historical question: MS-DOS

V

VanguardLH

Yousuf said:
PATH: ...!news.bnb-lp.com!not-for-mail
That's your NNTP server. It's the injection node in the PATH header.
They hide behind a private domain registration (i.e., their registrar
lists themself as the contact for that domain instead of the real
registrant of that domain). There is usually a bad reason why a
registrant chooses to hide, or the reason is superfluous (like trying to
avoid spam for domain renewals when obviously the e-mail address given
by the registrant to the registrar could be a special-use account that
filters out all e-mails except those that come from their registrar).
The host name news.bnb-lp.com equates to IP address 67.225.189.77 which
is allocated to Liquid Web (liquidweb.com). Since Liquid Web is a
webhosting company, someone has an account there on which they are
running an NNTP server. From the bnb-lp.com web site, Ball and Ball is
yet another 3rd tier webhoster (they resell their provider's service)
along with providing Usenet access.

It's possible they don't carry some newsgroups that other NNTP servers
carry. Based on their primitive web site and that they are NOT a Usenet
backbone provider (e.g., Highwinds), and because it looks like they only
carry text-only newsgroups (which is a bit pricey at $30/yr), it's quite
possible they don't carry some newsgroups. *.msdos may be some of those
they don't carry. Some NNTP servers don't carry as many newsgroups as
others (and some carry lots of garbage newsgroups).

Have your newsreader refresh its list of newsgroups; i.e., have it
re-read the list of groups from the NNTP server. Then search on
"msdos". I'm using Albasani as my NNTP provider and they show 16 groups
with *.msdos for a name. Eternal-September has the same newsgroups.
There are few in Albasani that aren't on Eternal-September and visa
versa but most are duplicated on all NNTP servers.
 
V

VanguardLH

GreyCloud said:
That doesn't have any of the internal or external commands. While most
MS-DOS installs use the default command interpreter (command.com), it is
possible to specify a different program (i.e., you get a different
shell). The 'shell' or 'comspec' parameters in config.sys specified
which command interpreter to load; if omitted, the kernel used the
default one (command.com). That specified the primary shell. The
secondary shell was specified using the COMSPEC environment variable
(e.g., 4DOS.COM).

The internal commands are those provided by the command interpreter
(command.com, 4dos.com, etc), not by io.sys. The external commands were
actually just programs bundled with the OS. They also were not buried
somewhere inside of io.sys.

If you read that Wiki article, you'll see that io.sys has nothing to do
with what internal and external commands are available or from where
they are retrieved.
 
G

glee

Yousuf Khan said:
Yeah, I know you posted that, but I didn't get a chance to respond to
it since it was getting late for me. However, I also wanted some
additional verification about it. Funny, the C:\DOS directory seems so
logically simple, but I can't remember that at all. Then I would
assume, the IBM version had a C:\PCDOS directory?
PCDOS 7 (and probably the earlier versions) used C:\DOS
 
V

VanguardLH

David said:
They couldn't all be in the root as there was a limit of 64 files in
the root.
Depends on the storage media which was never mentioned. For example, a
360KB 5.25" floppy has 7 sectors allocated to the FAT, sectors are 512
bytes in size, and each entry (file or directory) consumes 32 bytes in
the FAT, so that floppy can hold 112 entries:

7 sectors * 512 bytes/sector / 32 bytes/entry = 112 entries

Summary of maximum entry count for MS/PC-DOS (root folder only):
8" 250 KB floppy: 68
8" 500 KB floppy: 68
8" 1.2 MB floppy: 192
5.25" 180 KB floppy: 64
5.25" 360 KB floppy: 112
5.25" 1.2 MB floppy: 224
3.5" 720 KB floppy: 112
3.5" 1.44 MB floppy: 224
3.5" 2.88 MB floppy: 240
3.5" 1.68 MB DMF floppy: 16 (*)
Hard disks FAT12/16/32: 512

(*) Microsoft apps were often distributed using these hence the need to
invent CAB files to deliver a larger number of files.

Not all media formats are listed above. Many more are listed at
http://en.wikipedia.org/wiki/Floppy_disk but I wasn't going to waste
time to check what were they max entry count in the root folder. For an
alternate listing of "Root dir entries" on media size, read
http://support.microsoft.com/kb/75131.

If long filenames are supported then the max count goes down due to use
of more bytes per entry in the FAT to store the alternate long name.

MS-DOS 2.0 introduced directories that could hold a lot more files and
[sub]directories: 4068 for FAT12, 64K for FAT16, 268,173,300 for FAT32
(using the default cluster sizes). That didn't alleviate the maximum
entry count in the root folder.

Are we having fun yet roaming down reminiscence lane?
 
G

GreyCloud

That doesn't have any of the internal or external commands. While most
MS-DOS installs use the default command interpreter (command.com), it is
possible to specify a different program (i.e., you get a different
shell). The 'shell' or 'comspec' parameters in config.sys specified
which command interpreter to load; if omitted, the kernel used the
default one (command.com). That specified the primary shell. The
secondary shell was specified using the COMSPEC environment variable
(e.g., 4DOS.COM).

The internal commands are those provided by the command interpreter
(command.com, 4dos.com, etc), not by io.sys. The external commands were
actually just programs bundled with the OS. They also were not buried
somewhere inside of io.sys.

If you read that Wiki article, you'll see that io.sys has nothing to do
with what internal and external commands are available or from where
they are retrieved.
IO.sys is the device driver file.
MSDOS.SYS is what loads command.com from all that I could gather.
All you have to do to test this out is to rename command.com to
tcommand.com. Then reboot. If cd c:\ doesn't work, then the question
has been answered. Just a test case.
 
V

VanguardLH

GreyCloud said:
IO.sys is the device driver file.
MSDOS.SYS is what loads command.com from all that I could gather.
All you have to do to test this out is to rename command.com to
tcommand.com. Then reboot. If cd c:\ doesn't work, then the question
has been answered. Just a test case.
Yep, as you have asserted, the internal commands are from the command
interpreter (aka shell) that msdos.sys loads. It might be command.com.
It could be something different (e.g., 4dos.exe). That something loaded
the command interpreter does not equate to that something being the
command interperter where are the internal commands. If you want to
proceed further backwards, you could use your logic to say the internal
and external commands are in the BIOS since, after all, it starts the
entire loading process of the MBR bootstrap code which loads the boot
sector in the active primary partition which loads the kernel which
loads the command interpreter.
 
G

GreyCloud

Yep, as you have asserted, the internal commands are from the command
interpreter (aka shell) that msdos.sys loads. It might be command.com.
It could be something different (e.g., 4dos.exe). That something loaded
the command interpreter does not equate to that something being the
command interperter where are the internal commands. If you want to
proceed further backwards, you could use your logic to say the internal
and external commands are in the BIOS since, after all, it starts the
entire loading process of the MBR bootstrap code which loads the boot
sector in the active primary partition which loads the kernel which
loads the command interpreter.
In my experiences with MS-DOS, I've never seen 4dos.exe. The only thing
that I saw was command.com... msdos.sys & io.sys.
The bios usually has to do with low-level system calls. I used to have
the IBM reference books on those system calls, but never saw things like
CD, COPY, REN, etc. in their book.
I suppose I could fire up the old IBM I do have and try this myself.
 
D

David H. Lipman

From: "VanguardLH said:
David said:
They couldn't all be in the root as there was a limit of 64 files in
the root.
Depends on the storage media which was never mentioned. For example, a
360KB 5.25" floppy has 7 sectors allocated to the FAT, sectors are 512
bytes in size, and each entry (file or directory) consumes 32 bytes in
the FAT, so that floppy can hold 112 entries:

7 sectors * 512 bytes/sector / 32 bytes/entry = 112 entries

Summary of maximum entry count for MS/PC-DOS (root folder only):
8" 250 KB floppy: 68
8" 500 KB floppy: 68
8" 1.2 MB floppy: 192
5.25" 180 KB floppy: 64
5.25" 360 KB floppy: 112
5.25" 1.2 MB floppy: 224
3.5" 720 KB floppy: 112
3.5" 1.44 MB floppy: 224
3.5" 2.88 MB floppy: 240
3.5" 1.68 MB DMF floppy: 16 (*)
Hard disks FAT12/16/32: 512

(*) Microsoft apps were often distributed using these hence the need to
invent CAB files to deliver a larger number of files.

Not all media formats are listed above. Many more are listed at
http://en.wikipedia.org/wiki/Floppy_disk but I wasn't going to waste
time to check what were they max entry count in the root folder. For an
alternate listing of "Root dir entries" on media size, read
http://support.microsoft.com/kb/75131.

If long filenames are supported then the max count goes down due to use
of more bytes per entry in the FAT to store the alternate long name.

MS-DOS 2.0 introduced directories that could hold a lot more files and
[sub]directories: 4068 for FAT12, 64K for FAT16, 268,173,300 for FAT32
(using the default cluster sizes). That didn't alleviate the maximum
entry count in the root folder.

Are we having fun yet roaming down reminiscence lane?
Nah, we haven't touched QEMM, Extended vs. Expanded RAM ;-)

Thanx for the data correction.
 
G

Gene E. Bloch

From: "VanguardLH said:
David said:
They couldn't all be in the root as there was a limit of 64 files in
the root.
Depends on the storage media which was never mentioned. For example, a
360KB 5.25" floppy has 7 sectors allocated to the FAT, sectors are 512
bytes in size, and each entry (file or directory) consumes 32 bytes in
the FAT, so that floppy can hold 112 entries:

7 sectors * 512 bytes/sector / 32 bytes/entry = 112 entries

Summary of maximum entry count for MS/PC-DOS (root folder only):
8" 250 KB floppy: 68
8" 500 KB floppy: 68
8" 1.2 MB floppy: 192
5.25" 180 KB floppy: 64
5.25" 360 KB floppy: 112
5.25" 1.2 MB floppy: 224
3.5" 720 KB floppy: 112
3.5" 1.44 MB floppy: 224
3.5" 2.88 MB floppy: 240
3.5" 1.68 MB DMF floppy: 16 (*)
Hard disks FAT12/16/32: 512

(*) Microsoft apps were often distributed using these hence the need to
invent CAB files to deliver a larger number of files.

Not all media formats are listed above. Many more are listed at
http://en.wikipedia.org/wiki/Floppy_disk but I wasn't going to waste
time to check what were they max entry count in the root folder. For an
alternate listing of "Root dir entries" on media size, read
http://support.microsoft.com/kb/75131.

If long filenames are supported then the max count goes down due to use
of more bytes per entry in the FAT to store the alternate long name.

MS-DOS 2.0 introduced directories that could hold a lot more files and
[sub]directories: 4068 for FAT12, 64K for FAT16, 268,173,300 for FAT32
(using the default cluster sizes). That didn't alleviate the maximum
entry count in the root folder.

Are we having fun yet roaming down reminiscence lane?
Nah, we haven't touched QEMM, Extended vs. Expanded RAM ;-)
Groan!

Can't say that I miss that aspect of things.
 
G

Gene E. Bloch

In my experiences with MS-DOS, I've never seen 4dos.exe. The only thing
that I saw was command.com... msdos.sys & io.sys.
Because you didn't buy and install 4dos.

It was an independent product.
 
K

Ken Blake

Because you didn't buy and install 4dos.

It was an independent product.

It was a *wonderful* product (although I can hardly remember the
details of it, I remember liking it very much). But I do remember once
writing a batch file of about 4000 lines!
 
A

Ant

Nah, we haven't touched QEMM, Extended vs. Expanded RAM ;-)
No no! XMS, EMS, conventional memory (EVIL!!), config.sys, autoexec.bat,
etc. :D
--
"When you need a helpline for breakfast cereals, it's time to start
thinking about tearing down civilization and giving the ants a go."
--Chris King in a.s.r.
/\___/\ Ant(Dude) @ http://antfarm.ma.cx (Personal Web Site)
/ /\ /\ \ Ant's Quality Foraged Links: http://aqfl.net
| |o o| |
\ _ / If crediting, then use Ant nickname and AQFL URL/link.
( ) If e-mailing, then axe ANT from its address if needed.
Ant is currently not listening to any songs on this computer.
 
A

Ant

No no! XMS, EMS, conventional memory (EVIL!!), config.sys, autoexec.bat,
etc. :D
Oh remember, DoubleSpace, Stacker, etc.? ;)
--
"An ant is a wise creature for itself, but it is a shrewd thing in an
orchard or garden." --Francis Bacon
/\___/\ Ant(Dude) @ http://antfarm.ma.cx (Personal Web Site)
/ /\ /\ \ Ant's Quality Foraged Links: http://aqfl.net
| |o o| |
\ _ / If crediting, then use Ant nickname and AQFL URL/link.
( ) If e-mailing, then axe ANT from its address if needed.
Ant is currently not listening to any songs on this computer.
 
Y

Yousuf Khan

It's possible they don't carry some newsgroups that other NNTP servers
carry. Based on their primitive web site and that they are NOT a Usenet
backbone provider (e.g., Highwinds), and because it looks like they only
carry text-only newsgroups (which is a bit pricey at $30/yr), it's quite
possible they don't carry some newsgroups. *.msdos may be some of those
they don't carry. Some NNTP servers don't carry as many newsgroups as
others (and some carry lots of garbage newsgroups).

Have your newsreader refresh its list of newsgroups; i.e., have it
re-read the list of groups from the NNTP server. Then search on
"msdos". I'm using Albasani as my NNTP provider and they show 16 groups
with *.msdos for a name. Eternal-September has the same newsgroups.
There are few in Albasani that aren't on Eternal-September and visa
versa but most are duplicated on all NNTP servers.
Not to prolong this sideline discussion much further, the problem was
not whether or not they carried the newsgroups, it's whether or not I
even searched for one, because I was not aware of them.

Yousuf Khan
 
Y

Yousuf Khan

In my experiences with MS-DOS, I've never seen 4dos.exe. The only thing
that I saw was command.com... msdos.sys & io.sys.
The bios usually has to do with low-level system calls. I used to have
the IBM reference books on those system calls, but never saw things like
CD, COPY, REN, etc. in their book.
I suppose I could fire up the old IBM I do have and try this myself.
4DOS was an alternate command.com, which you had to buy separately. The
company behind it eventually sold the rights to it to Norton, which
appropriately renamed it to NDOS. Exact same functionality as 4DOS, but
different name. It basically was an improved command.com with many
advanced features dedicated to making the user interface easier (history
recall, sophisticated DOS-based menu creation, etc., etc.). If you're
familiar with Linux or Unix, think of it like being the difference
between "bash" and "sh": i.e. basically exactly the same functionality
and then some.

Back in those days I also used to multitask DOS programs using Desqview.
The combination of Desqview and 4DOS was probably the ultimate
command-line oriented operating system for PC's.

Yousuf Khan
 

Ask a Question

Want to reply to this thread or ask your own question?

You'll need to choose a username for the site, which only take a couple of moments. After that, you can post your question and our members will help you out.

Ask a Question

Top