| 1. |
Solve : hELP Cannot find OS? |
|
Answer» I have installed MSdos 71 on my old HP Vectra 386 but I cant get it to boot up. After bios its says 'Cannot FIND operating system' then it hangs. There is no other OS on this system. When I use a startup floppy for WIN 98 to get to dos prompt and I type autoexec, then MSdos starts up. I have done the sys c: and it was a success, I even tried tinkering with MSDos.sys file but after several fdisk /mbr, rebuilding mbr etc, I am still not able to boot from C: hard drive. Then the HDD is failing Thanks Patio, by mentioning the HD, u remind me of info that I forgot to mention here which is, Im using an 8gig SSD and its brand new. Does it make any difference? I dont have a spare dynamic drive I can try out to see if it does. Ok after 1 week of tinkering, I installed Dos 6.22, transferred the system files and wallah, I GOT a bootable hard disk. One thing I discovered from all my experience which I think might be useful for some readers on here is that, most of the current Dos software out there that have been written in the last 5 to 10 years like Freedos, mbr utilities etc, are actually written with Linux. Not all Bios can read Linux. When u stick in a bootable floppy that is coded in Linux, it wont boot, u will see a few dots on the screen then it will hang. I also noticed that if u used any of these so called Dos utilities that are code with Linux to fdisk or format ur drive on such a old computer, earlier fdisk will not be able to read such drive. Not true at all if the boot stik is built proper...Quote from: modobo on July 09, 2018, 08:00:06 PM most of the current Dos software out there that have been written in the last 5 to 10 years like Freedos, mbr utilities etc, are actually written with Linux. Not all Bios can read Linux. When u stick in a bootable floppy that is coded in Linux, it wont boot, u will see a few dots on the screen then it will hang. I also noticed that if u used any of these so called Dos utilities that are code with Linux to fdisk or format ur drive on such a old computer, earlier fdisk will not be able to read such drive. What you are describing is when something is Linux, not whether something is "coded in" Linux. A lot of utilities are based on the Linux Kernel. (memtest for example). And Kernel version 3.8 dropped support for the 386; it has nothing to do with the "BIOS not reading Linux"- instead the kernel is hanging/crashing during the boot process itself. |
|