I downloaded msdos 5.0 diskimage but disk 1 won't start!

July 9, 2020 at 07:38:03
Specs: Windows
I download Ms-dos 5.0 from Allfiles.com and Pcjs.org even bough dos 3.31 startup disk from Ebay. All I get is non system disk! I downloaded a boot disk for dos 5.0 that lets me in to start page but keep asking for disk 1 when disk 1 is in A: drive. I have hated Disk image ever sense it came out in the 90's.

message edited by ericflemming


See More: I downloaded msdos 5.0 diskimage but disk 1 wont start!


#1
July 9, 2020 at 09:04:45
The 'non system' error likely means the disk doesn't have the dos boot files, io.sys and msdos.sys, or they're not in the right place on the disk. Go to bootdisk.com to download files to create any bootdisk you need. There's no reason to buy them on ebay.

When installing dos 6.22 I found that if the disk in the drive doesn't have the correct disk label (created with the dos LABEL command) it will keep asking you to insert the correct disk. In that case, run the label command (I think the syntax is label a:, where a: is the drive with the disk). When it asks for a new label type disk, hit the space bar 6 times (I think) and type 1 or 2, whichever number the disk is, then 'enter'. LABEL is an external dos command so you'll need to access it from whichever disk it's located on or from an already working system. Anyway that's probably the problem you're having with installing dos 5.


Reply ↓  Report •

#2
July 9, 2020 at 13:34:05
Should not pay for stuff that old. Maybe if you try a different download site....
https://winworldpc.com/product/ms-d...

Reply ↓  Report •

#3
July 9, 2020 at 14:48:26
First, if you have "images" of disks, then you have to write them to another disk (using something like Winimage or some other utility).

Second, it's possible you have a faulty floppy drive as well. Do any other disks work (other than the "Disk1 of the supposed DOS5 disk)?

Third, is this a 3.5" (720KB/1.44MB/2.88MB) or 5.25" (360K/1.2MB) floppy drive?

"Channeling the spirit of jboy..."

message edited by T-R-A


Reply ↓  Report •

Related Solutions

#4
July 11, 2020 at 14:59:47
I,ve tried win 95 boot disk and it would boot up and show A: drive. So I know the drive is OK. I downloaded DiskISO for the disk image. And it works fine. I even created a boot disk by coping to a floppy from a list of files that is suppose to be on the disk. That didn't work ether. I went to winworld none of them worked ether. I think the label is the problem. but I don't have a label command. I have tryed dos 4.01 making boot disks with sys,io,msdos,fdisk,format,command and still can't get the computer to start up. I am trying to bring a compuadd 386 back to life and a compaq deskpro 16 figured out the voltage to be 4.7 so now it's holding it's bios memory. The thing with that old compaq it requires specific hard drives. I disk image the dos 5.0 from the downloads and put it into floppy drive. So I should not have had a problem with labeling. Can you tell me more about the labeling program?

message edited by ericflemming


Reply ↓  Report •

#5
July 11, 2020 at 18:53:51
(Another edit) If you're creating a bootdisk from scratch rather than an image file (it sounds like you've tried both):

When you create a boot disk you need to do a format a: /s where the /s transfers the system files after the format or if you don't need to format just type sys a:. Either way copies the system files to the disk. It's important to transfer the system files rather than just copying them because they need to be at the correct place on the disk else the disk may not boot. Of the 3 system files, io.sys and msdos.sys are normally hidden files, while the third, command.com, shows with the dir command. Hidden files on the a: drive can be viewed with dir a: /a:h or with the 'attrib' command.

Note that the system files that are transferred are the ones the computer was booted with. So if you want to create a dos 5 bootdisk you need to boot the computer with dos 5. Once the system files are transferred you can copy whatever files you want to the disk. However you can't mix command files from different dos versions. If you do you get an 'incorrect dos version' error when you try to run one of them. Well, there is a way around that using the 'setver' command but for a basic bootdisk that would be an unnecessary complication.

The 'label' command has been available since dos 3.1 so assuming you have all the command files for your dos versions then it should be there. If the system files are correct then the system will boot even if the label is wrong. It only becomes a problem when you continue with installing dos on the hard drive.

I don't know why your downloaded image files aren't working. Usually it won't matter what dos or windows version you use when creating disks from images as dos command files wouldn't be involved. As T-R-A says, make sure the images you download are for the disks you're using. And if you create a disk and it boots the computer to an a:\> prompt then you did it right. Any problem after that is something else.

If you still can't get it going I can probably email you self-extracting image files for dos 6.22.

message edited by DAVEINCAPS


Reply ↓  Report •

#6
July 12, 2020 at 16:42:09
I manage to get a working boot disk that gets me into A: It's dos 5.0 but I am still having the problem of in stalling the rest of the dos 5.0 keep asking for disk 1. All dos 5.0 are disk image so it a direct copy from disk image. I type "setup" it start to go thru the first few setups. Then when it show the copying to hard drive it ask for disk 1. The disk image 1 that I just copied. I can't get pass that point. I hit enter it ask for disk 1 or I have to hit f3 to escape. This is the error message I get "insert the disk labeled Ms-dos 5.0 disk 1 into drive A: " I loaded a label.exe on the disk and put such info on the disk. Still no go.

message edited by ericflemming


Reply ↓  Report •

#7
July 12, 2020 at 21:57:35
When you run the label command what does it show as the current label? What I mentioned in my #1 above works for dos 6.22 and I just assume it's the same with dos 5. I probably still have some dos 5 disks somewhere. If I can find them I'll check their software label.

Another option is to manually install the files. You'd do a sys c: after booting from the dos 5 disk, Make a dos directory and then manually uncompress each file to that dos directory.


Reply ↓  Report •

#8
July 13, 2020 at 09:48:07
I found out why the dos 5.0 disk image downloads won't work. WinWorld has removed the volume directory file. The file stating what disk it is.

Reply ↓  Report •

#9
July 13, 2020 at 11:52:45
Were you able to install dos 5 then or is the missing file preventing that?

Reply ↓  Report •

#10
July 13, 2020 at 13:02:42
Nope still having problems with Dos5.0 I even made a c:/dos prompt loaded all the files in and tried to run setup that way. It still asked for disk 1. so no go.

Reply ↓  Report •

#11
July 13, 2020 at 13:05:52
I have Microsoft Windows graphic environment that I want to load into the computer but it needs dos to run.

Reply ↓  Report •

#12
July 13, 2020 at 18:46:37
Once you copied the files to the hard drive you can't run 'setup' as it assumes you're installing from floppy disks.

I found 2 dos 5 on 5.25 disks and one on 720k. I viewed the 720K ones. The label was as I said in my #1 above. The command to manually expand the compressed files on the disk is 'expand.exe' but officially it was only included with dos 6 and above although you may be able to find a version that works for dos 5 as some sites say it was available for dos 5. So check your disks to see if they include 'expand.exe'. Here's some info about it:

https://jeffpar.github.io/kbarchive...

If so you can manually install dos by expanding each compressed file. Most but not all of the disk files will be compressed. A compressed file, for example 'attrib', will show as 'attrib .ex_' and the expanded version will be 'attrib.exe'. And you wouldn't want to copy any file named 'setup' or that would start that mess again if you ran it.

Don't copy any file named autoexec.bat or config.sys. Those are files that automatically run after the system files load and if they're on the floppy disks they're likely associated with setup.

If you don't have the expand file here's a download:

http://www.conradshome.com/win31/

but I have no idea if it'll run with dos 5.

The manual install sequence would be:

Boot with a dos 5 bootdisk
Type sys c: and enter.
Type md c:\dos
Copy the files from the floppies to c:\dos, using the expand command when necessary (Expand instruction in first link above)

Anyway that's what you'd have to do to install dos 5 manually if you can't get setup to run.

I can still try sending you the 6.22 disks that I know will work. . .

message edited by DAVEINCAPS


Reply ↓  Report •

#13
July 13, 2020 at 23:01:49
I checked the 720K disks again and 'expand.exe' was on the third one (I blame cataracts) so likely it's on one of your disks too. It'll need to be on the disk or directory (C:\dos, for example) you're using. Anyway, review the link above about using expand and decide if you want to try a manual install.

Reply ↓  Report •

#14
July 14, 2020 at 07:30:14
I printed up a list that show what dos is suppose to have per version. And the one I got from ether ( Pcjr, allboot, or WinWorld) are missing files one of them happens to be dos01l 400. That's for dos 4.01 it is all so missing XMAEM.SYS. At lease the disk image files I downloaded. I did find the expand file. Thank you very much! that is helping a lot. And it's start to fire up some old neurons I should have keep my old packard bell 386sx but it couldn't do much not even expand. I had to switch to a different mother board. Now that I know why it's not working I might be able to fix it. I ran into this problem a long time ago and had to hunt down the file on the net. Looks like I'll be doing it again. thanks for your help Dave.

Reply ↓  Report •

#15
July 14, 2020 at 09:51:05
You're welcome.

Some of the versions of dos put together by computer manufacturers included additional files that microsoft didn't have on their official releases. It doesn't hurt to have those additional files but they may not be necessary for your setup. Later today I'll post back a directory list of the files on the disks I have.


Reply ↓  Report •

#16
July 14, 2020 at 13:38:25
The disks are an upgrade. The dos command files will be the same as a full version but setup checks to see if you have a previous version of dos installed. They appear to be microsoft retail disks:

Disk 1
ANSI.SY_ AUTOEXEC.BAT CGA.VI_
COMMAND.CO_ COUNTRY.SY_ DEBUG.EX_ DISPLAY.SY_ DOSKEY.CO_
EDLIN.EX_ EGA.CP_ EGA.SY_ EMM386.EX_ FASTOPEN.EX_
FDISK.EX_ FORMAT.CO_ HDBKUP.EXE HIMEM.SY_
IO.SY_ KEYB.CO_ KEYBOARD.SY_ MEM.EX_ MIRROR.CO_
MODE.CO_ MSDOS.SY_ NLSFUNC.EX_ RAMDRIVE.SY_ README.1ST
SETUP.EXE SETUP.INI SETVER.EX_ SHARE.EX_ SMARTDRV.SY_
SYS.CO_ UNDELETE.EX_ UNFORMAT.COM UNINSTAL.EX_ XCOPY.EX_

Disk 2
CGA.GR_ CGA.IN_ DOSHELP.HL_
DOSSHELL.CO_ DOSSHELL.EX_ DOSSHELL.HL_ DOSSWAP.EX_ EDIT.COM
EDIT.HL_ EGA.GR_ EGA.IN_ EGA.VI_ EGAMONO.GR_
HDRSTORE.EXE HELP.EX_ HERC.GR_ HERC.VI_
MONO.GR_ MONO.IN_ MSHERC.CO_ PACKING.LST PRINT.EX_
QBASIC.EX_ QBASIC.HL_ RECOVER.EX_ VGA.GR_ VGA.VI_
VGAMONO.GR_

Disk 3
4201.CP_ 4208.CP_ 5202.CP_
APPEND.EX_ APPNOTES.TXT ASSIGN.CO_ ATTRIB.EX_ BACKUP.EX_
CHKDSK.EX_ COMP.EX_ CV.COM DELOLDOS.EX_ DISKCOMP.CO_
DISKCOPY.CO_ DMDRVR.BI_ DRIVER.SY_ EXE2BIN.EX_ EXPAND.EXE
FC.EX_ FIND.EX_
GORILLA.BA_ GRAFTABL.CO_ GRAPHICS.CO_ GRAPHICS.PR_ IPX.OB_
JOIN.EX_ LABEL.EX_ LCD.CP_ LOADFIX.CO_ MONEY.BA_
MORE.CO_ NET.EX_ NET5.CO_ NETBEUI.DO_ NETWKSTA.1X_
NETWKSTA.2X_ NIBBLES.BA_ PRINTER.SY_ README.TXT REDIR.1X_
REDIR.2X_ REMLINE.BA_ REPLACE.EX_ RESTORE.EX_ SETNAME.EX_
SORT.EX_ SSTOR.SY_ SUBST.EX_ TBMI2.CO_ TREE.CO_
WINA20.38_ XBIOS.OV_

As you can see most are compressed. If you use EXPAND you have to supply the complete file name.
Offhand I'm not sure of some of the file extensions since the last letter on compressed file extensions is missing but it shouldn't be too difficult to find out. Also, my disk 1 doesn't seem to be bootable as the system files are compressed, making them unusable until they're expanded.

message edited by DAVEINCAPS


Reply ↓  Report •

#17
July 14, 2020 at 14:32:18
Well I am missing 29 files and some of the one's I have are bad so I done playing around with this I wasted 6 days with these sigh,s Thanks for your help! I am going to just buy the disks off ebay and if they are bad it going to get right back. I am done spending money for nothing.

Reply ↓  Report •

#18
July 14, 2020 at 20:25:25
Yeah, I know the feeling--putting a lot of time into something, making some headway, but in the end it just doesn't work out.

Some files probably wouldn't be installed--readme's, setup files and packing.lst--and some are optional, for example the .BA_ are basic files you'd run with qbasic and not really needed. As I recall the dosshell files give the screen a more graphic interface--not like windows but better than dos. I don't think I ever used it.

Well good luck. Let us know how it goes.

message edited by DAVEINCAPS


Reply ↓  Report •

#19
July 22, 2020 at 05:57:16
Well I was able to get dos 4.01 to work after all which is all I need. But had to in stall everything the hard way and after I put disk one in hit setup it started working.Went threw the hole processes. So now the computer will start up on it's own. Funny thing the dos 5 even in up grade still ask for the first disk.

Reply ↓  Report •

#20
July 22, 2020 at 21:45:32
So it's working OK with dos 4? I'm not sure why the dos 5 upgrade is still giving that message, unless we're back to an incorrect label.

Reply ↓  Report •

#21
July 26, 2020 at 08:11:58
I don't understand why ether. I like to use dos 5 it's easier to work with and it's what the computer is suppose to have. These old computer had a lot of quarks. And was very finicky on what was in it.

Reply ↓  Report •

Ask Question