Well, I did some research on everything and found the cause of the problem.
First, I confirmed that what the tool does is this:
1) The partition table is moved from sector 0 to sector 1
2) Some code is written to sector 0. This code asks for a password and if
you fail, you can't boot.
I found the problem to be in initdisk.c, function ScanForPrimaryPartitions.
What happens is that when the tool has moved the partition table to sector
1, startSector here is 1... and this line:
partitionStart = startSector + pEntry->RelSect;
makes partitionStart be 64 in my case (because RelSect is 63 on this
drive)... and the real start of the partition IS at sector 63!
If I manually remove startSector from there so partitionStart is always 63,
the protection from the tool is effective and it boots, and everything works
well.
Will this "fix" cause problems with some drives?? Is it safe to leave
startSector out of that line?
Thanks for any clue.....
--
View this message in context:
http://www.nabble.com/Boot-sector-not-standard--tf2471283.html#a6909759
Sent from the FreeDOS - User mailing list archive at Nabble.com.
-------------------------------------------------------------------------
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
