-------- Original-Nachricht --------
Betreff: Re: [Freedos-user] SYS.COM
Datum: Sun, 05 Nov 2006 04:20:04 -0500
Von: Kenneth J. Davis <[EMAIL PROTECTED]>
An: freedos-user@lists.sourceforge.net
CC: [EMAIL PROTECTED]
Norbert Remmel wrote:
> Hi,
>
> Having discussed some stuff with eric before, Eric suggested to start a
> new discussion on the mailing list.
>
> There is a problem concerning SYS.COM using dual boot systems
> Windows XP / FreeDOS
>
> Windows XP always looks for dos system files on its boot partition and
> changes the attributes of the found files to system, hidden and readonly.
> If you use SYS.COM to replace existing FreeDOS files by newer ones,
> SYS.COM always writes a new bootsecor and after that it tries to replace
> kernel.sys and command.com.
> But getting to the point where command.com is about to be replaced
> SYS.COM outputs an error code followed by an error message and doesn't
> proceed.
>
> To get things work you have to change command.com's attributes to only
> archive by using attrib. After that you can restart SYS.COM to have the
> FreeDOS system files replaced without error.
>
> I would suggest two things to change in SYS.COM.
> At first SYS.COM should replace the FreeDOS system files no matter what
> attributes are set for command.com.
sounds reasonable
So when running sys, if kernel.sys is readonly (and/or system and/or
hidden) should it sys:
a) fail as it currently does
b) ask the user 1st, then remove the attributes and overwrite the
existing kernel
c) without asking the user, remove the attributes and overwrite the
existing kernel
d) rename the existing kernel to something like kernel.001 (where
the actual # could be incremented to next non-conflicting one) and then
copy over the new kernel
e) other suggestions?
> Second, when used on dual boot systems, it would be great to have an
> option to only replace the FreeDOS system files without renewing the
> bootsector 'cause writing a new bootsetor results in an unbootable
> Windows XP. To change this back to normal you always have to start the
> recovery console and run FIXBOOT to overwrite the newly written FreeDOS
> bootsector or you have to use third party tools to do the same job.
this is easy, don't use sys, just copy the kernel.sys file yourself. If
you don't need to replace the boot sector, there really is no reason to
use sys. In general, once you have a booting FreeDOS system, there is
almost no reason to replace the bootsector or rerun sys again.
>
> Regards
>
> Norbert.
Jeremy
(this still probably won't make it to the list, so feel free to forward
for me :-)
-------------------------------------------------------------------------
Using Tomcat but need to do more? Need to support web services, security?
Get stuff done quickly with pre-integrated technology to make your job easier
Download IBM WebSphere Application Server v.1.0.1 based on Apache Geronimo
http://sel.as-us.falkag.net/sel?cmd=lnk&kid=120709&bid=263057&dat=121642
_______________________________________________
Freedos-user mailing list
Freedos-user@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/freedos-user
