Hi!
14-Мар-2004 18:25 [EMAIL PROTECTED] (Jim Lilly) wrote to "Arkady
V.Belousov" <[EMAIL PROTECTED]>:
JL> I got kernel 2033_32 and used INSTALL.BAT to create a FreeDOS bootable
JL> Booted fine!
Perfect.
JL> Note; this particular ZIP disk WAS FAT32 before transferring system
JL> files. Note; This disk remains seen as FAT32 under WinXP
Jim, please, retest with latest bootfix version (1.3) - now it analyzes
not only default, but also current BPB. I hope, current BPB should be equal
with boot record on your FAT32 diskette. Also, now under XP bootfix should
say about boot sector reading error (used another method to detect that
reading is unsuccessful).
JL> Files in [JLilly.zip];
Archive is broken: for result and screen01.bmp CRC check fails.
JL> Result - done prior to transferring system files (when ZIP-100 was
JL> still FAT32 & NOT bootable)
After updating kernel default BPB now shown as FAT32, not FAT16 (as
previously):
______________O\_/_________________________________\_/O______________
Checking drive C:
Reading default BPB...
Bytes/sector : 512
Sectors/cluster : 1
FAT start, size : 32, 1512 * 2
Root cluster : 2
Total sectors : 0, 196576
Hidden sectors : 32
Sectors/track, heads : 32, 64
Version, mirror flags : 0000h, 00h
Info, backup sectors : 1, 6
Media ID : F8h
Done.
Volume is a FAT32.
Reading boot sector...
Bytes/sector : 512
Sectors/cluster : 2
FAT start, size : 36, 762 * 2
[...]
Drive, media ID, FS : 00h, F8h, "FAT32 "
Serial#, label : 5062FD5Fh, "NO NAME "
Done.
_____________________________________________________________________
O/~\ /~\O
Difference is only that default BPB offers less cluster size. This
increases FATs area by 1500 sectors (750k), but allows to place more (small)
files.
JL> reslt2 - done after transferring system files. ZIP disk now bootable
Yes, result is same (except that SYS uses special FFh value for drive
number). So, there was a bug in kernel, which was used previously. This
should be reported for those, who prepare ISO images: beta9rc4 is outdated
and definitely should be updated.
JL> screen01.bmp - fdisk /info screen capture
File is broken. :(
JL> screen02.bmp - fdisk /status screen capture
JL> screen03.bmp - fdisk /dump screen capture (AFTER system files were
JL> transferred)
There are no fdisk/fump, only successful run of SYS.
JL> screen04.bmp - SYS C: screen capture of system files transfer to a
JL> FAT32 ZIP-100 disk, prepped by SpinRite. Was unbootable. But after
JL> system files transfer is now bootable. Note errors captured on screen.
This (error in creating C:\KERNEL.SYS by SYS) is, probably, result of
running SYS under older kernel? I think, if you now boot under newer kernel,
then this error will disappear.
-------------------------------------------------------
This SF.Net email is sponsored by: IBM Linux Tutorials
Free Linux tutorial presented by Daniel Robbins, President and CEO of
GenToo technologies. Learn everything from fundamentals to system
administration.http://ads.osdn.com/?ad_id70&alloc_id638&op=click
_______________________________________________
Freedos-kernel mailing list
[EMAIL PROTECTED]
https://lists.sourceforge.net/lists/listinfo/freedos-kernel
