Freedos FAT Kernel GO! <hang>
Daniel Jensen
Freedos mailing list or send email to it, so I'll post this here:
Whenever I attempt to boot freedos (from GRUB) it gets to Freedos FAT
Kernel GO! and then hangs. Here's my config:
FreeDos (NC1+kernel with fat32 fix) is on the second partition of a
4GB harddrive on an IBM thinkpad (600E). Partition table is as
follows:
1 type 83, linux ext3, 2559 MB
2 type 6, fat16, 1090 MB
3 type 82, linux swap, 260 MB
My Grub conf for Freedos is rootnoverify (hd0,1), makeactive, and
chainloader +1. I have tried with just plain root (hd0,1) instead of
rootnoverify and with chainloader /bootsect.fd (after doing a sys c:
c:\bootsect.fd), all to no avail.
I'm new to Freedos and wasn't able to find any information on this
other than the suggestion to do /bootsect.fd. Any tips would be
appreciated. (I would also appreciate it if somebody could forward
this to the freedos mailing list, fd-...@topica.com.)
Joe Fischer
: Ok, for some reason (problem with topica?) I'm unable to join the
: Freedos mailing list or send email to it, so I'll post this here:
:
: Whenever I attempt to boot freedos (from GRUB) it gets to Freedos FAT
: Kernel GO! and then hangs. Here's my config:
:
: FreeDos (NC1+kernel with fat32 fix) is on the second partition of a
: 4GB harddrive on an IBM thinkpad (600E). Partition table is as
: follows:
: 1 type 83, linux ext3, 2559 MB
: 2 type 6, fat16, 1090 MB
: 3 type 82, linux swap, 260 MB
Usually MSDOS has to be totally within the first
2 gigs, perhaps at least some versions of FreeDOS also
have that problem, as FAT16 systems can only see a drive
as 2 gigs.
I use mobile racks with extra trays for changing
small 2 gig hard drives to eliminate the problems with
the growing pain problems of the operating systems and
the older BIOS'.
I don't know if this is your problem or not.
Joe Fischer
--
3
Daniel Jensen
> Usually MSDOS has to be totally within the first
> 2 gigs, perhaps at least some versions of FreeDOS also
> have that problem, as FAT16 systems can only see a drive
> as 2 gigs.
So- are there any versions/configurations of FreeDOS which don't have this problem?
Joe Fischer
I don't know, you mentioned a FAT32 fix, so I will
look for that. Does linux have to be in the first 2 gigs?
Joe Fischer
--
3
Martin Str|mberg
: Joe Fischer <grav...@shell1.iglou.com> wrote:
:> Usually MSDOS has to be totally within the first
:> 2 gigs, perhaps at least some versions of FreeDOS also
:> have that problem, as FAT16 systems can only see a drive
:> as 2 gigs.
I've never heard that FreeDOS has this problem. However kernels
current at the time of the Beta8 release did have to be within the
first 1024 cylinders (which translates to ~8GB).
Some later kernel version corrected this as well.
All above is IIRC.
Right,
MartinS
Victor Vlasenko
"Daniel Jensen" <jen...@iname.com> wrote in message
news:593999a2.03030...@posting.google.com...
1024 cylinder.
You may try the latest kernel : 2028ax
http://freedos.sourceforge.net/emm386/ke2028ax.zip
Daniel Jensen
> Yes, all kernels after version 2027test allow boot partition to be above
> 1024 cylinder.
> You may try the latest kernel : 2028ax
> http://freedos.sourceforge.net/emm386/ke2028ax.zip
OK, I've already been using ke2028ax (that's what I meant by "kernel
with fat32 fix"), so this isn't the problem.
Victor Vlasenko
> OK, I've already been using ke2028ax (that's what I meant by "kernel
> with fat32 fix"), so this isn't the problem.
tries to execute it. Than kernel.sys should immediately (after unpacking
itself) show '1' at the next line, then '2' and then '3', so the output
should look like:
FreeDOS FAT Kernel GO!
123
If it is not true, then
1. You could try the 2026b or older kernel (maybe there is some bug in the
LBA boot sector code, introduced in >= 2027test kernels).
2. There was some error while unpacking the kernel. (To work around this you
could try to recompile the kernel yourself, and turn off UPXing it)
3. Most probably the boot code loaded wrong data. You could write down your
hard disk and partition geometry using fdisk and then look through the
boot.asm code...
PS. If you are intrested you could contact me privately to try to resolve
the problem.
Victor
Kevin Lawton
gigs, or 8 gigs - it can be anywhere within the bounds accessible by the
bios and partition table. What does have to be near the 'front' of the disk
is the boot loader (GRUB, LILO, Boot Magic, etc) to which the MBR (master
boot record) points.
The 2 gig and 8 gig limits come into play when you use a Microsoft-style
bootloader. Also FAT 16 partitions have to each be no more than 2 gig in
size, though you can have several 2 gig FAT 16 partitions within a larger
drive. AFAIK a FAT 16 partition lying outside of the 8 gig boundary on a
drive will not be bootable.
Hope this helps clarify it.
Kevin.
"Joe Fischer" <grav...@shell1.iglou.com> wrote in message
news:3e6c3...@news.iglou.com...