DOS question

[philo]

> >
> Thanks, will do that.
>
> Somethings not quite normal, yet.
>
> I want to install DOS 6,22, my disks say with disk #1 inserted, reboot
> and setup will start, it did yesterday at some point, but today on reboot
> it says "Invalid system disk, replace disk....."
>
> Would have thought that would go OK. My 6.22 disks are IIRC, the MS DOS
> version.
>
> Guess a question is: how to install, maybe copy files to C with a real
> directory this time, run it from C, although that may not work with this.
>
> ms


Did you leave a floppy in the drive?

If so remove it.

otherwise just boot with an msdos boot floppy from the same version as is on
the machine
then issue the command sys C:

 

[ms]

"philo" <philo@privacy.net> wrote in
news:uOanwXPQIHA.3388@TK2MSFTNGP03.phx.gbl:

>
>
>> >
>> Thanks, will do that.
>>
>> Somethings not quite normal, yet.
>>
>> I want to install DOS 6,22, my disks say with disk #1 inserted,
>> reboot and setup will start, it did yesterday at some point, but
>> today on reboot it says "Invalid system disk, replace disk....."
>>
>> Would have thought that would go OK. My 6.22 disks are IIRC, the MS
>> DOS version.
>>
>> Guess a question is: how to install, maybe copy files to C with a
>> real directory this time, run it from C, although that may not work
>> with this.
>>
>> ms
>
>
> Did you leave a floppy in the drive?
>
> If so remove it.
>
> otherwise just boot with an msdos boot floppy from the same version as
> is on the machine
> then issue the command sys C:
>
Did that awhile ago. The system files must already be there as w/o boot
disk it boots fine to C prompt. And command.com is in C root.

ms

 

[philo]

>>
>>
>> Did you leave a floppy in the drive?
>>
>> If so remove it.
>>
>> otherwise just boot with an msdos boot floppy from the same version as
>> is on the machine
>> then issue the command sys C:
>>
> Did that awhile ago. The system files must already be there as w/o boot
> disk it boots fine to C prompt. And command.com is in C root.
>
> ms


yep that's what's supposed to happen

 

[ms]

ms <ms@invalid.com> wrote in news:5so4j4F1acjvbU1@mid.individual.net:

> "Ben Myers" <benjmyers@mindR-e-m-o-v-Espring.com> wrote in
> news:#Ps6pTOQIHA.6036@TK2MSFTNGP03.phx.gbl:
>
>> "ms" <ms@invalid.com> wrote in message
>> news:5snvrhF19ircnU2@mid.individual.net...
>>> "Ben Myers" <benjmyers@mindR-e-m-o-v-Espring.com> wrote in
>>> news:enWyucNQIHA.2376@TK2MSFTNGP02.phx.gbl:
>>> Ben, thanks, you are always helpful.
>>> Having tried other things, finally your help above did the trick, as
>>> Philo mentioned earlier. A boot disk from that site has all the
>>> needed
>>
>>> files on one disk, no install is necessary, which helped in this
>>> case. Everything worked fine, fdisk, format, boots up to a DOS 6.22
>>> C
>> prompt.
>>> No W95 mention at all. It is finally a true DOS machine.
>>> Now, one minor glitch, each bootup it asks for confirm date and
>>> time, maybe thats a DOS default to live with.
>>
>> Create a "c:\autoexec.bat" file. It can be empty or one that
>> actually does something.
>>
>> Ben
>>
> Thanks, will do that.
>
> Somethings not quite normal, yet.
>
> I want to install DOS 6,22, my disks say with disk #1 inserted, reboot
> and setup will start, it did yesterday at some point, but today on
> reboot it says "Invalid system disk, replace disk....."
>
> Would have thought that would go OK. My 6.22 disks are IIRC, the MS
> DOS version.
>
> Guess a question is: how to install, maybe copy files to C with a real
> directory this time, run it from C, although that may not work with
> this.
>
> ms

Hope someone has ideas on this. I just did a search for DOS newsgroups, I
found very few with any activity, even alt.dos.batch has only about 5
posts in the past month.

ms

 

[... et al.]

Don Phillipson wrote:

> 1. From this prompt, do
> DIR D*.*
> This will generate a directory of all files and
> folders beginning with D
> but only in the folder where you are currently
> logged. To be sure you are in the root directory
> do a couple of times
> CD..
> that is C D dot dot (with no spaces)

Except when i mistype i always separate Attributes and Switches
from the Command by a space!
But wow! Booted in to Win98SE's 'Command Prompt only' and tested
this and it works without any spaces. Wow again.


> DOS is "unforgiving" in that every keystroke
> must be correct.

Kinda not in this case (at least DOS under Win98SE).

'CD ..' or 'CD..' -> both backs up the path one level.

My DOS 5 reference indicate a space, but 'CD /?' suggests your
lingo. 'CD/?' works as well .. LOL.


--
Nah-ah. I'm staying out of this. ... Now, here's my opinion.

Please followup in the newsgroup.
E-mail address is invalid due to spam-control.

 

[ms]

ms <ms@invalid.com> wrote in news:5sokbnF1a3masU1@mid.individual.net:

> ms <ms@invalid.com> wrote in news:5so4j4F1acjvbU1@mid.individual.net:
>
>> "Ben Myers" <benjmyers@mindR-e-m-o-v-Espring.com> wrote in
>> news:#Ps6pTOQIHA.6036@TK2MSFTNGP03.phx.gbl:
>>
>>> "ms" <ms@invalid.com> wrote in message
>>> news:5snvrhF19ircnU2@mid.individual.net...
>>>> "Ben Myers" <benjmyers@mindR-e-m-o-v-Espring.com> wrote in
>>>> news:enWyucNQIHA.2376@TK2MSFTNGP02.phx.gbl:
>>>> Ben, thanks, you are always helpful.
>>>> Having tried other things, finally your help above did the trick,
>>>> as Philo mentioned earlier. A boot disk from that site has all the
>>>> needed
>>>
>>>> files on one disk, no install is necessary, which helped in this
>>>> case. Everything worked fine, fdisk, format, boots up to a DOS 6.22
>>>> C
>>> prompt.
>>>> No W95 mention at all. It is finally a true DOS machine.
>>>> Now, one minor glitch, each bootup it asks for confirm date and
>>>> time, maybe thats a DOS default to live with.
>>>
>>> Create a "c:\autoexec.bat" file. It can be empty or one that
>>> actually does something.
>>>
>>> Ben
>>>
>> Thanks, will do that.
>>
>> Somethings not quite normal, yet.
>>
>> I want to install DOS 6,22, my disks say with disk #1 inserted,
>> reboot and setup will start, it did yesterday at some point, but
>> today on reboot it says "Invalid system disk, replace disk....."
>>
>> Would have thought that would go OK. My 6.22 disks are IIRC, the MS
>> DOS version.
>>
>> Guess a question is: how to install, maybe copy files to C with a
>> real directory this time, run it from C, although that may not work
>> with this.
>>
>> ms
>
> Hope someone has ideas on this. I just did a search for DOS
> newsgroups, I found very few with any activity, even alt.dos.batch has
> only about 5 posts in the past month.
>
> ms
>

The boot sequence may be the problem. If it looks to A first, that would
explain the message.

ms

 

[Marcus Red]

ms wrote:
> "Brian A." <gonefish'n@afarawaylake> wrote in news:#eRquqDQIHA.5980
> @TK2MSFTNGP04.phx.gbl:
>
>> Sorry, should be:
>>
>> Leave the C out and type:
>>
>> cd dos
>>
>
> Thanks, Brian
>
> cd DOS
>
> "invalid directory"
>
> I took pains to use caps for the directory as it was named in caps.
>
> It boots up with the W95 logo and message starting W95 again as before the
> Fdisk work, as if I didn't change anything, so still a puzzle.
>
> ms
Well it's too late now, but the reason you couldn't CD DOS is that "DOS"
is a file very likely the last one that "copy a:*.* c:\dos" overwrote -
if there isn't a directory called c:\DOS then "copy" ASSuMEs that the
target is a filename.
You needed to have "md c:\dos" first.

 

[Brian A.]

"Marcus Red" <admin@127.0.0.1> wrote in message
news:XVQ9j.18521$KC3.15058@newsfe6-gui.ntli.net...

> Well it's too late now, but the reason you couldn't CD DOS is that "DOS" is a file
> very likely the last one that "copy a:*.* c:\dos" overwrote - if there isn't a
> directory called c:\DOS then "copy" ASSuMEs that the target is a filename.
> You needed to have "md c:\dos" first.
>

From the OPs original post:
<quote>
Rebooted to (W95) C prompt.

Copied the 3 DOS install disks to a new DOS directory in C.

Rebooted, DIR at C shows the DOS directory
</quote>


--

Brian A. Sesko { MS MVP_Shell/User }
Conflicts start where information lacks.
http://basconotw.mvps.org/

Suggested posting do's/don'ts: http://www.dts-l.org/goodpost.htm
How to ask a question: http://support.microsoft.com/kb/555375

 

[Ben Myers]

"ms" <ms@invalid.com> wrote in message news:5so4j4F1acjvbU1@mid.individual.net...
> "Ben Myers" <benjmyers@mindR-e-m-o-v-Espring.com> wrote in
> news:#Ps6pTOQIHA.6036@TK2MSFTNGP03.phx.gbl:
> Somethings not quite normal, yet.
> I want to install DOS 6,22, my disks say with disk #1 inserted, reboot
> and setup will start, it did yesterday at some point, but today on reboot
> it says "Invalid system disk, replace disk....."

Sounds like the computer is having trouble reading the floppy. To test it,
try it on another computer or use ScanDisk in thorough or surface scan mode.
Concerning the floppy drive in the problem computer, you might try cleaning
it or replacing it with a known good drive.

> Would have thought that would go OK. My 6.22 disks are IIRC, the MS DOS
> version.
> Guess a question is: how to install, maybe copy files to C with a real
> directory this time, run it from C, although that may not work with this.

It is my understanding that DOS 6.22 setup checks the volume label
for each floppy, so running setup from the hard drive may be difficult.
Since the DOS 6.22 system files are already installed on the computer,
you might just go ahead with your plans and deal with problems as they
occur.

Ben

 

[ms]

"Ben Myers" <benjmyers@mindR-e-m-o-v-Espring.com> wrote in
news:#hbJw3YQIHA.2268@TK2MSFTNGP02.phx.gbl:

> "ms" <ms@invalid.com> wrote in message
> news:5so4j4F1acjvbU1@mid.individual.net...
>> "Ben Myers" <benjmyers@mindR-e-m-o-v-Espring.com> wrote in
>> news:#Ps6pTOQIHA.6036@TK2MSFTNGP03.phx.gbl:
>> Somethings not quite normal, yet.
>> I want to install DOS 6,22, my disks say with disk #1 inserted,
>> reboot
>
>> and setup will start, it did yesterday at some point, but today on
> reboot
>> it says "Invalid system disk, replace disk....."
>
> Sounds like the computer is having trouble reading the floppy. To
> test it, try it on another computer or use ScanDisk in thorough or
> surface scan mode. Concerning the floppy drive in the problem
> computer, you might try cleaning it or replacing it with a known good
> drive.
>
>> Would have thought that would go OK. My 6.22 disks are IIRC, the MS
> DOS
>> version.
>> Guess a question is: how to install, maybe copy files to C with a
>> real
>
>> directory this time, run it from C, although that may not work with
> this.
>
> It is my understanding that DOS 6.22 setup checks the volume label
> for each floppy, so running setup from the hard drive may be
> difficult. Since the DOS 6.22 system files are already installed on
> the computer, you might just go ahead with your plans and deal with
> problems as they occur.
>
> Ben
>
Thanks, Ben, some things to look at.

I would like to, if possible, load DOS 6.22 as it offers a reasonable DOS
shell menu. Otherwise I have to load Xtree. I used to know Xtree, but it
takes a good memory (human) for all those keystrokes, which I don't have
at my age.

I will open another thread, as I can't get into BIOS.

ms

 

[ms]

"Ben Myers" <benjmyers@mindR-e-m-o-v-Espring.com> wrote in
news:#hbJw3YQIHA.2268@TK2MSFTNGP02.phx.gbl:

>
> Sounds like the computer is having trouble reading the floppy. To
> test it, try it on another computer or use ScanDisk in thorough or
> surface scan mode. Concerning the floppy drive in the problem
> computer, you might try cleaning it or replacing it with a known good
> drive.
>
The floppy reads fine in another computer.

ms

 

[dadiOH]

Brian A. wrote:
> "Marcus Red" <admin@127.0.0.1> wrote in message
> news:XVQ9j.18521$KC3.15058@newsfe6-gui.ntli.net...
>
>> Well it's too late now, but the reason you couldn't CD DOS is that
>> "DOS" is a file very likely the last one that "copy a:*.* c:\dos"
>> overwrote - if there isn't a directory called c:\DOS then "copy"
>> ASSuMEs that the target is a filename.
>> You needed to have "md c:\dos" first.
>>
>
> From the OPs original post:
> <quote>
> Rebooted to (W95) C prompt.
>
> Copied the 3 DOS install disks to a new DOS directory in C.
>
> Rebooted, DIR at C shows the DOS directory
> </quote>

Well, that's what he *thought* he was doing. I'm betting that Marcus
is right and that ms's DIR showed him a file named "DOS"...that he
never made a directory.


--

dadiOH
____________________________

dadiOH's dandies v3.06...
....a help file of info about MP3s, recording from
LP/cassette and tips & tricks on this and that.
Get it at http://mysite.verizon.net/xico

 

[Brian A.]

"dadiOH" <dadiOH@guesswhere.com> wrote in message
news:OiUu3kaQIHA.3916@TK2MSFTNGP02.phx.gbl...
> Brian A. wrote:
>> "Marcus Red" <admin@127.0.0.1> wrote in message
>> news:XVQ9j.18521$KC3.15058@newsfe6-gui.ntli.net...
>>
>>> Well it's too late now, but the reason you couldn't CD DOS is that
>>> "DOS" is a file very likely the last one that "copy a:*.* c:\dos"
>>> overwrote - if there isn't a directory called c:\DOS then "copy"
>>> ASSuMEs that the target is a filename.
>>> You needed to have "md c:\dos" first.
>>>
>>
>> From the OPs original post:
>> <quote>
>> Rebooted to (W95) C prompt.
>>
>> Copied the 3 DOS install disks to a new DOS directory in C.
>>
>> Rebooted, DIR at C shows the DOS directory
>> </quote>
>
> Well, that's what he *thought* he was doing. I'm betting that Marcus
> is right and that ms's DIR showed him a file named "DOS"...that he
> never made a directory.
>
>
> --
>

A likely possiblity it could have been a file instead of a directory. Since ms
never mentioned either way and we can't see his machine, only he could explain what
he did and what he saw. That waters under the bridge and passed by at this point in
time.



--

Brian A. Sesko { MS MVP_Shell/User }
Conflicts start where information lacks.
http://basconotw.mvps.org/

Suggested posting do's/don'ts: http://www.dts-l.org/goodpost.htm
How to ask a question: http://support.microsoft.com/kb/555375

 

[Don Phillipson]

> "Ben Myers" <benjmyers@mindR-e-m-o-v-Espring.com> wrote in
> news:#hbJw3YQIHA.2268@TK2MSFTNGP02.phx.gbl:
>
> > Sounds like the computer is having trouble reading the floppy. To
> > test it, try it on another computer or use ScanDisk in thorough or
> > surface scan mode. Concerning the floppy drive in the problem
> > computer, you might try cleaning it or replacing it with a known good
> > drive.

"ms" <ms@invalid.com> wrote in message
news:5sqbtkF1acelsU2@mid.individual.net...

> The floppy reads fine in another computer.

This seems to confirm that you should replace the
floppy drive as recommended. These things do not
last for ever . . .

--
Don Phillipson
Carlsbad Springs
(Ottawa, Canada)

 

[ms]

"Brian A." <gonefish'n@afarawaylake> wrote in
news:#lnfzMbQIHA.3400@TK2MSFTNGP03.phx.gbl:

> "dadiOH" <dadiOH@guesswhere.com> wrote in message
> news:OiUu3kaQIHA.3916@TK2MSFTNGP02.phx.gbl...
>> Brian A. wrote:
>>> "Marcus Red" <admin@127.0.0.1> wrote in message
>>> news:XVQ9j.18521$KC3.15058@newsfe6-gui.ntli.net...
>>>
>>>> Well it's too late now, but the reason you couldn't CD DOS is that
>>>> "DOS" is a file very likely the last one that "copy a:*.* c:\dos"
>>>> overwrote - if there isn't a directory called c:\DOS then "copy"
>>>> ASSuMEs that the target is a filename.
>>>> You needed to have "md c:\dos" first.
>>>>
>>>
>>> From the OPs original post:
>>> <quote>
>>> Rebooted to (W95) C prompt.
>>>
>>> Copied the 3 DOS install disks to a new DOS directory in C.
>>>
>>> Rebooted, DIR at C shows the DOS directory
>>> </quote>
>>
>> Well, that's what he *thought* he was doing. I'm betting that Marcus
>> is right and that ms's DIR showed him a file named "DOS"...that he
>> never made a directory.
>>
>>
>> --
>>
>
> A likely possiblity it could have been a file instead of a
> directory. Since ms
> never mentioned either way and we can't see his machine, only he could
> explain what he did and what he saw. That waters under the bridge and
> passed by at this point in time.
>
>
It was simply that the copy parameters worked, but my path statement was
wrong, it's been years since I used DOS, so tried to copy to a new
directory, DOS does not do that, have to create the directory first, then
copy files into it. The result was the intended directory name, but was
actually empty.

Sorry that I exercised you folks when the dirctory did not exist, but I
learned how to detect it in this thread.

ms

 

[ms]

"Don Phillipson" <d.phillipsonSPAMBLOCK@rogers.com> wrote in
news:ONjh5OcQIHA.536@TK2MSFTNGP06.phx.gbl:

>> "Ben Myers" <benjmyers@mindR-e-m-o-v-Espring.com> wrote in
>> news:#hbJw3YQIHA.2268@TK2MSFTNGP02.phx.gbl:
>>
>> > Sounds like the computer is having trouble reading the floppy. To
>> > test it, try it on another computer or use ScanDisk in thorough or
>> > surface scan mode. Concerning the floppy drive in the problem
>> > computer, you might try cleaning it or replacing it with a known
good
>> > drive.
>
> "ms" <ms@invalid.com> wrote in message
> news:5sqbtkF1acelsU2@mid.individual.net...
>
>> The floppy reads fine in another computer.
>
> This seems to confirm that you should replace the
> floppy drive as recommended. These things do not
> last for ever . . .
>

Don, I should have included that the machine's floppy drive works fine,
that was a possibility, but not the solution. If I could get into BIOS
and change the boot sequence, I think that would do it.

ms

 

[dadiOH]

ms wrote:

> Don, I should have included that the machine's floppy drive works
> fine, that was a possibility, but not the solution. If I could get
> into BIOS and change the boot sequence, I think that would do it.

Why?

1. You have no DOS (or other OS) on the HD.
2. You are trying to install to HD DOS from floppies. Without
success.
3. You want to copy the install floppies to HD and use the HD data to
install.

If you do #3 and then dump A: from the boot chain then how, pray tell,
do you think you are going to access the HD? It does not compute...


--

dadiOH
____________________________

dadiOH's dandies v3.06...
....a help file of info about MP3s, recording from
LP/cassette and tips & tricks on this and that.
Get it at http://mysite.verizon.net/xico

 

[ms]

"dadiOH" <dadiOH@guesswhere.com> wrote in news:#P$#0ajQIHA.5692
@TK2MSFTNGP02.phx.gbl:

> ms wrote:
>
>> Don, I should have included that the machine's floppy drive works
>> fine, that was a possibility, but not the solution. If I could get
>> into BIOS and change the boot sequence, I think that would do it.
>
> Why?
>
> 1. You have no DOS (or other OS) on the HD.
> 2. You are trying to install to HD DOS from floppies. Without
> success.
> 3. You want to copy the install floppies to HD and use the HD data to
> install.
>
> If you do #3 and then dump A: from the boot chain then how, pray tell,
> do you think you are going to access the HD? It does not compute...
>
>

I came to that conclusion when I posted about that, and stated it.

As usual, your post is not helpful.

ms

 

[dadiOH]

ms wrote:
> "dadiOH" <dadiOH@guesswhere.com> wrote in news:#P$#0ajQIHA.5692
> @TK2MSFTNGP02.phx.gbl:
>
>> ms wrote:
>>
>>> Don, I should have included that the machine's floppy drive works
>>> fine, that was a possibility, but not the solution. If I could get
>>> into BIOS and change the boot sequence, I think that would do it.
>>
>> Why?
>>
>> 1. You have no DOS (or other OS) on the HD.
>> 2. You are trying to install to HD DOS from floppies. Without
>> success.
>> 3. You want to copy the install floppies to HD and use the HD
>> data to install.
>>
>> If you do #3 and then dump A: from the boot chain then how, pray
>> tell, do you think you are going to access the HD? It does not
>> compute...
>>
>>
>
> I came to that conclusion when I posted about that, and stated it.

You did? I quoted what you posted when I replied to it. I did not
and do not see your conclusion, do you?
_____________

> As usual, your post is not helpful.

And as usual your posts and replies are generally a morass of
unsnipped verbiage that is unnecessary and which makes finding
something very difficult. This one happens to be one of the rare
exceptions but only because others had already snipped.

Also as usual you are thrashing about trying to do something about
which you haven't a clue. Which is good in a way as it gives others
in the group something to do. Have you considered a hobby other than
computers?

--

dadiOH
____________________________

dadiOH's dandies v3.06...
....a help file of info about MP3s, recording from
LP/cassette and tips & tricks on this and that.
Get it at http://mysite.verizon.net/xico

 

[Bill in Co.]

dadiOH wrote:
> ms wrote:
>> "dadiOH" <dadiOH@guesswhere.com> wrote in news:#P$#0ajQIHA.5692
>> @TK2MSFTNGP02.phx.gbl:
>>
>>> ms wrote:
>>>
>>>> Don, I should have included that the machine's floppy drive works
>>>> fine, that was a possibility, but not the solution. If I could get
>>>> into BIOS and change the boot sequence, I think that would do it.
>>>
>>> Why?
>>>
>>> 1. You have no DOS (or other OS) on the HD.
>>> 2. You are trying to install to HD DOS from floppies. Without
>>> success.
>>> 3. You want to copy the install floppies to HD and use the HD
>>> data to install.
>>>
>>> If you do #3 and then dump A: from the boot chain then how, pray
>>> tell, do you think you are going to access the HD? It does not
>>> compute...
>>>
>>>
>>
>> I came to that conclusion when I posted about that, and stated it.
>
> You did? I quoted what you posted when I replied to it. I did not
> and do not see your conclusion, do you?
> _____________
>
>> As usual, your post is not helpful.
>
> And as usual your posts and replies are generally a morass of
> unsnipped verbiage that is unnecessary and which makes finding
> something very difficult. This one happens to be one of the rare
> exceptions but only because others had already snipped.
>
> Also as usual you are thrashing about trying to do something about
> which you haven't a clue. Which is good in a way as it gives others
> in the group something to do. Have you considered a hobby other than
> computers?

That wasn't very nice, Don. Come on now, you can be a little bit more of
a gentleman than that. Old school values? Nevermind, I'm probably
dating myself.