Re: [Freedos-user] SYS A: C:

2006-06-16 Thread Eric Auer

On Fri, 16 Jun 2006, Johnson Lam wrote:
 On Thu, 15 Jun 2006 23:41:13 +0100, you wrote:
 5. SYS B: C: /oem:ms (it says system transferred)

Which it probably did...


 When I reboot with the C drive marked Active I get two dots on a black
 screen and a flashing cursor, that wasn't expected...
 I suggest SYS should check the target to see it's bootable or not,
 otherwise don't report System Transferred since FDISK's default
 worry about your previous record and did not write anything to the
 hard disk.

I disagree: That would force SYS to look at areas which
it is not supposed to touch at all (partition table,
maybe even analyze the boot menu configuration of WinNT/XP/2k/2k3
or Linux). I myself, when installing DOS on a harddisk, always
install it at a place which is THEN made accessible by adding
a menu item to an existing boot menu. If SYS would force DOS to
be booted directly (you said MS SYS or MS FDISK or MS FORMAT
sometimes does that kind of thing), it would destroy the boot
menu, and if SYS would say System not transferred, DOS will
probably not be booted, then that would confuse users. Plus it
would be hard / almost impossible to teach SYS to analyze the
configuration of all common boot menu systems.

Eric



___
Freedos-user mailing list
Freedos-user@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/freedos-user


Re: [Freedos-user] SYS A: C:

2006-06-16 Thread Gerry Hickman
Hi Eric,

 5. SYS B: C: /oem:ms (it says system transferred)
 
 Which it probably did...

Yes, but there's obviously some major problems with this. To be fair, 
it's probably unreasonable to expect FreeDOS to be able to install an 
MS-DOS 6.22 boot sector from a FAT12 floppy to a FAT16 partition. It 
would certainly be unreasonable to expect FreeDOS to be able to install 
an MS-DOS 6.22 boot sector from a FAT12 floppy to a FAT32 partition!

However, I don't see why there can't be a simple program to install a 
bootsector from a saved location as follows:

MS-DOS 6.22 - FAT16
Win95/98 - FAT32

In a previous post on the topic, it was suggested this isn't easy 
because the boot sector contains drive geometry information and 
therefore you can't just save bootsectors and expect to be able to 
restore them back again. I don't know if this is true or not, but I've 
certainly done similar things with WinImage and it worked fine, but 
maybe WinImage is able to calculate geometry??

-- 
Gerry Hickman (London UK)


___
Freedos-user mailing list
Freedos-user@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/freedos-user


Re: [Freedos-user] SYS A: C:

2006-06-15 Thread Gerry Hickman
Gerry Hickman wrote:

 OK, I guess I could use a FAT16 partition instead; if I do this, is 
 there some way to install the DOS 6.22 boot sector to C: without 
 actually inserting a floppy? e.g. read the saved boot sector from somewhere?

OK, I tried it with a FAT16 partition

1. FDISK /PRIO:2000
2. FDISK /ACTIVATE:1
3. FORMAT C: (YES)
4. Insert DOS 6.22 floppy into drive B:
5. SYS B: C: /oem:ms (it says system transferred)

When I reboot with the C drive marked Active I get two dots on a black 
screen and a flashing cursor, that wasn't expected...

-- 
Gerry Hickman (London UK)


___
Freedos-user mailing list
Freedos-user@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/freedos-user


Re: [Freedos-user] SYS A: C:

2006-06-15 Thread Johnson Lam
On Thu, 15 Jun 2006 23:41:13 +0100, you wrote:

Hi,

5. SYS B: C: /oem:ms (it says system transferred)

When I reboot with the C drive marked Active I get two dots on a black 
screen and a flashing cursor, that wasn't expected...

I suggest SYS should check the target to see it's bootable or not,
otherwise don't report System Transferred since FDISK's default
worry about your previous record and did not write anything to the
hard disk.


Rgds,
Johnson.


___
Freedos-user mailing list
Freedos-user@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/freedos-user


Re: [Freedos-user] SYS A: C:

2006-06-13 Thread Gerry Hickman
Hi Jeremy,

 Based on your other message and this one; I never got around to writing 
 the FAT32 boot sector, so at the moment MS/PC DOS are only supported by 
 FD sys for FAT12 and FAT16 hence your problems.

OK, I guess I could use a FAT16 partition instead; if I do this, is 
there some way to install the DOS 6.22 boot sector to C: without 
actually inserting a floppy? e.g. read the saved boot sector from somewhere?

-- 
Gerry Hickman (London UK)


___
Freedos-user mailing list
Freedos-user@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/freedos-user


Re: [Freedos-user] SYS A: C:

2006-06-12 Thread Gerry Hickman

 So I should have issued
 
 SYS B: C:
 
 It probably still won't work, but at least I'll be using the correct 
 command.

OK, this time it found the MS-DOS boot sector on the floppy and said 
something like MS boot sector not supported:(

-- 
Gerry Hickman (London UK)


___
Freedos-user mailing list
Freedos-user@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/freedos-user


Re: [Freedos-user] SYS A: C:

2006-06-09 Thread Kenneth J. Davis
Gerry Hickman wrote:

 Hi,
 
 Today I did this from a FreeDOS bootable CD;
 
 1. Use FDISK to delete all primary partitions, but leave MBR
 2. FDISK /PRI:2000 (2Gb FAT32 Ext13)
 3. FDISK /Activate:1 (boot to first primary at next HD reboot) reboot
 3. FORMAT C: say yes to confirm
 
 I now have an empty working C: drive with FreeDOS boot sector
 
 I insert an MS-DOS 6.22 system floppy into A: and type
 
 SYS A: C:
 
 (I want to install MS-DOS boot-sector, IO.SYS and MSDOS.SYS to C:)
 
 What happens next?? It installs FreeDOS boot sector, and kernel to the C 
 drive!! That's not what I told it to do...
 

Where (what drive) are sys, kernel.sys, io.sys  msdos.sys on?
Or more clearly is kernel.sys and sys on the same (current) drive and 
the MS-DOS files (io.sys  msdos.sys) on A:, so instead of looking at 
the source drive sys appears to be using the kernel from the current 
drive?  or are all three on the same drive, in which case you must 
specify using the /OEM:MS (I think) option so that the FreeDOS kernel is 
ignored, as default search order [which you may have found a bug in] 
will assume you want boot the FreeDOS kernel before any other DOSes 
(unless sys is compiled for Enhanded DR-DOS, in which case it flips FD 
with EDR kernel names in its list).  Also please let me know which 
version of sys you are using.

Thanks,
Jeremy





___
Freedos-user mailing list
Freedos-user@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/freedos-user