Recent changes to feature-requests

#18 Please stabilize 2.5.3 version!

2019-03-17T00:50:43.476000Z

status: open --> closed

#18 Please stabilize 2.5.3 version!

2019-03-17T00:50:17.741000Z

Version 2.6.0 released as stable with no changes compared to 2.5.3

#18 Please stabilize 2.5.3 version!

2019-03-05T20:42:27.891000Z

Thanks for your encouraging words! I will probably release a stable labeled 2.6 version identical to 2.5.3. But being short on time I first want to make a new release of my splitjob project. I was hoping to do that release in october but haven't had the time since even development is finisched..

Please stabilize 2.5.3 version!

2019-03-05T04:25:40.297000Z

Since current development version 2.5.3 very stable and useful please stabilize this version. This need because some distributin such http://www.system-rescue-cd.org does not include it referring to the fact that is development version. Please change information about new stable version on main project download page: http://ms-sys.sourceforge.net/#Download

Thanx for your work!

Please stabilize 2.5.3 version!

2019-03-05T04:25:40.297000Z

Ticket 18 has been modified: Please stabilize 2.5.3 version!
Edited By: Henrik Carlqvist (henca)
Status updated: u'open' => u'closed'

#17 mkdosfs boot sector and -m option for message file

2018-12-12T20:06:15.441000Z

Priority: 5 --> 8

#17 mkdosfs boot sector and -m option for message file

2018-12-12T20:04:41.866000Z

ms-sys is not intended to replace tools which create file systems like mkfs.fat. Ms-sys is only intended to make disks and file systems bootable. Before running ms-sys on a file system you will need to use some other tool to create the file system. That tool migt add a text explaining that the file system is not bootable, but once the file system has been made bootable by ms-sys or some other tool that text will be overwritten by program code and other messages.

mkdosfs boot sector and -m option for message file

2018-12-12T04:28:03.680000Z

Hello,

i am very satisfied with ms-sys version 2.5.3 because i creates nearly
all usual boot sectors. But for me missing is the boot sector produced
by the mkfs.fat alias mkfs.vfat or mkdosfs command, which is part of
the DOS files system tools. The code for the initial program loader of
that tool just writes a message on screen with instructions for the user.

By default these 2 lines look like:
This is not a bootable disk. Please insert a bootable floppy and
press any key to try again ...

Unfortunately i am not a programmer person. So i am not able to
implement this boot sector in side ms-sys source. The source code for
that loader stands as bytes sequence variable dummy_boot_code together
with assembler instructions in c-source file mkfs.fat.c in source
directory "src" of the DOS files system tools package
"dosfstools-master.zip".
So for an expert it should be easy to add that special boot sector to
the ms-sys tool.

Another feature of the dosfstools i like is the -m option. According
to man page mkdosfs(8) by this option the content of given file (not
exceeding 418 bytes) is used as displayed text instead of standard
english text. So for my german users i can display an according message
text in their own language like:
Dies ist kein startfähiges Laufwerk. Bitte legen Sie ein bootfähiges Medium ein
und drücken Sie eine beliebige Taste, um es erneut zu versuchen ...

So would be nice if the dosfstools bootsector and the "-m" option
could be implemented in a future version of ms-sys tool.

Thanks in advance and regards
Jörg Jenderek

mkdosfs boot sector and -m option for message file

2018-12-12T04:28:03.680000Z

Ticket 17 has been modified: mkdosfs boot sector and -m option for message file
Edited By: Henrik Carlqvist (henca)
_priority updated: u'5' => u'8'

#16 Need a Windows 10 boot

2017-03-04T08:03:39.362000Z

Only writing an MBR to the disk will not be enough to boot a drive. The partition with the boot flag set will also need some boot record (possible to create with flags like -2, -e or -3). Also the partition will need to contain some files that the boot record points to. Such files might have names like io.sys and msdos.sys.

A dd of a boot record will not be enough to create support for such a boot record. Information about different parts of the boot record is needed. In the case of an MBR information is needed about which part of the MBR contains the partition table. Also info about data of any other variable information like disk geometries is needed. If data didn't vary between different systems it would be easy to copy boot records by simply using dd instead of ms-sys.

regards Henrik