Re: setting up BIOS loader - difference in mkdisk and sys
- From: "Luca Calligaris" <l.calligaris.nospam@xxxxxxxxxxxxxxxxx>
- Date: Fri, 21 Aug 2009 15:02:32 +0200
You do not have to use the DOS sys command since you do not need a DOS
system disk. (sys will copy DOS system files -command.com etc- to your
media).
once you have partitioned and formatted (without the /S options as you can
imagine) your media running mkdisk batch will copy some files (boot.ini,
etc) to your media and,
most importatnt thing at all, it will overwrite the DOS partition boot
sector with bsect.img. This code is the one which locates and executes the
BIOS bootloader (BLDR) which
in turns will copy the OS image nk.bin in memory and jump into it
--
Luca Calligaris (MVP-Windows Embedded)
l.calligaris.nospam@xxxxxxxxxxxxxxxxxx
www.eurotech.it
"Shani" <Shani@xxxxxxxxxxxxxxxxxxxxxxxxx> ha scritto nel messaggio
news:E7E56D1A-BC7E-4640-A827-63F45D4FF1F3@xxxxxxxxxxxxxxxx
Hi
I am trying to setup my Intel Atom dev platform to run WinCE 6.0.
In an article on "Setting up BIOS Loader"
(http://msdn.microsoft.com/en-us/library/ms900922.aspx), I read the
directions to use MKDISK command. However, in some other resources to
transfer the MSDOS system to storage device, it was advised to use SYS c:
command.
What is the difference in mkdisk and sys? Which one is preferred?
Thanks
Shani
.
- Follow-Ups:
- References:
- Prev by Date: setting up BIOS loader - difference in mkdisk and sys
- Next by Date: Re: Boot image on FlashDisk
- Previous by thread: setting up BIOS loader - difference in mkdisk and sys
- Next by thread: Re: setting up BIOS loader - difference in mkdisk and sys
- Index(es):
Relevant Pages
|