|
|
|
freedos 1.0 don't booth from c:
|
Original Message
|
Name: IW2EVK
Date: November 22, 2006 at 23:17:13 Pacific
Subject: freedos 1.0 don't booth from c:OS: freedos 1.0CPU/Ram: 486dx4Model/Manufacturer: nec vetra 550d |
Comment: Hi'
i'm changed os fronm ms dos 7.10 to fd1.0.
i've deleted primary partition on c: then make a new partition with fd fdisk, formatted with format.com of fd and installed fd 1.0
when i start the pc , passed the post the machine try from A: and stop the boting.
If i start fd1.0 from all work fine...
(note: i can read the directory on c: and can start the program on c:, but i can't starting os sytem from c:)
I've also transferred many time with sys A: c: booth command the os without results. Where is the problems...
Many thanks in advance Roberto IW2EVK Milan ,Italy
Report Offensive Message For Removal
|
|
Response Number 3
|
Name: IW2EVK
Date: November 23, 2006 at 23:15:53 Pacific
|
Reply: (edit)don't work again...
the command sys C: it's the same of sys a: C:
(see instruction on sys/?)
I've again deleted the old primary partition, create a new fat32 partition , set active, formatted, then from a: make sys c: the system search disk on a: , then stopped boot procedure(no message ..)
I've also tryed to rewrite MBR with fdisk/xo option with no results. Roberto
 Report Offensive Follow Up For Removal
|
|
Response Number 4
|
Name: IVO
Date: November 24, 2006 at 07:08:34 Pacific
|
Reply: (edit)Well, you are right about the FreeDOS SYS command format... don't blame me, I'm relaying on my memory as I run FreeDOS in a virtual machine presently out of work. What you posted seems to point out the problem is due to the scanning of the *empty* floppy drive while booting is in progress. If so, the trouble may be hardware related. As a workaround and to check the correctness of the above statement, try to set the boot sequence in BIOS as C: A: and see if the hard disk is recognized as bootable. I don't think it is a FreeDOS or software issue.
Report Offensive Follow Up For Removal
|
|
Response Number 5
|
Name: jboy
Date: November 25, 2006 at 15:40:02 Pacific
|
Reply: (edit)How big a drive is in this 486? Hard to imagine that FAT32 would be warranted - are you using overlay software? If I know the answer I'll tell you the answer, and if I don't, I'll just respond, cleverly--Donald Rumsfeld
Report Offensive Follow Up For Removal
|
|
Response Number 6
|
Name: IW2EVK
Date: November 27, 2006 at 04:30:00 Pacific
|
Reply: (edit)the disk is large 516Mb .
fd 1.0 and ms dos 7,10 proposing automatically fat 32 fat.
The problem in ONLY a try to install freedos
(ms dos, ptsdos, datalight dos and drdos work with no problems)
Thanks for your attentions.
Roberto per Ivo Luigi Bertani : contattami su marinelluccia1chiocciolatiscali.it
Report Offensive Follow Up For Removal
|
|
Response Number 7
|
Name: jboy
Date: November 27, 2006 at 14:59:52 Pacific
|
Reply: (edit)Well, they might 'propose' FAT32, but it wouldn't be a necessity. For sure, there would be no need for an overlay, a 486 BIOS should handle that OK. I don't know then - I haven't much experience with FreeDOS, but it sounds like you've done everything correctly - it's a bit of a mystery. You might try manually inputting the drive parameters in the CMOS - sometimes autodetect isn't perfect - although it's odd that other DOS versions work without problems If I know the answer I'll tell you the answer, and if I don't, I'll just respond, cleverly--Donald Rumsfeld
Report Offensive Follow Up For Removal
|
|
Response Number 8
|
Name: jboy
Date: November 27, 2006 at 18:41:02 Pacific
|
Reply: (edit).. maybe try a different download and a different diskette, in case one or the other was defective - beyond that, don't know what else to suggest If I know the answer I'll tell you the answer, and if I don't, I'll just respond, cleverly--Donald Rumsfeld
Report Offensive Follow Up For Removal
|
|
Response Number 9
|
Name: IW2EVK
Date: December 3, 2006 at 23:17:50 Pacific
|
Reply: (edit)i solve the ptoblem creating with ptsdos2000
fdisk a 16 bit ext lba primary partiton and formatting/u with format of fd1.0
the with sys the system is transferred and boot from c:
i suppose a problem in sys of fd 1.0 and in fdisk of fd1.0 (?) Thanks at all for suggests. Roberto iw2evk
Milan Italy
Report Offensive Follow Up For Removal
|
Use following form to reply to current message:
|
|
|
