Hello all, Preview 13 testing is still underway. So far, I have not received any reports of major bugs or serious hiccups. However, there is one serious issue that is yet to be resolved to my satisfaction. The MBR issue. When incompatible boot code already is present or if the USB image is drive C: (targeting D:), post install fails to boot. Since it shouldn’t blast existing boot code, I guess the first situation is ok. However, the second is more tricky. Why is sys not updating the MBR? If you force it with /BOOT or other option, you will run into the first problem.
As I see it, there are 4 solutions. 1) Don’t worry about it. Let the user fix it. 2) Write a program to figure out drive letter and test MBR, Blank force new, Exists leave it alone. 3) Like 2, except if it exists prompt user to blast it. 4) Don’t worry about it. But, always prompt user in advanced mode. 1 easiest solution 2 & 3 are a bit of a pain and require figuring out what drive and partition the kernel has assigned to a specific drive letter. 3 & 4 easy, but will require some more prompting and language translations. Thanks in advance. Jerome ------------------------------------------------------------------------------ Site24x7 APM Insight: Get Deep Visibility into Application Performance APM + Mobile APM + RUM: Monitor 3 App instances at just $35/Month Monitor end-to-end web transactions and take corrective actions now Troubleshoot faster and improve end-user experience. Signup Now! http://pubads.g.doubleclick.net/gampad/clk?id=272487151&iu=/4140 _______________________________________________ Freedos-devel mailing list Freedos-devel@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/freedos-devel
