> On Feb 12, 2016, at 10:26 PM, Eric Auer <e.a...@jpberlin.de> wrote: > > > Hi Don, to make a PESSIMISTIC GUESS about the following: > >> Downloaded and burned to CD. >> Lots of "Error writing to drive A: DOS area write protection violation >> attempted" errors. Is there reason I am getting this?
It booted from CD? The USB image wasn’t really setup for that. > > Yes. Apparently version 1.2pre12 still tries to use pipelines, which > in DOS always means using temp files, without setting the temp dir > to a location on ramdisk or (if available) on your target harddisk? Yes it did. Preview 11 would check for a pre-existing hard drive C: and if it was usable would setup a temp directory. then it would use that to attempt to import a couple things from the previous OS install. If it could not, it would just wait until later when there was a hard drive it could use for temp storage for the installation process. (This is why you had issues when the USB stick booted as read only) Preview 12: Just sets up a ram drive at startup, assumes all is well and moves on. However, there was some old code that got left behind and is probably causing the write protect issue. Preview 13: (coming soon) should resolve these issues. > > This also means that all data sent through pipelines will be lost. > > OPTIMISTICALLY, you MIGHT "simply" be suffering from a bug in how > the DOSLFN driver interacts with the install process. It seems to > cause A: access instead of access to the proper selected drive in > certain situations, but you and Rugxulo know more about this than > I, at this point ;-) You could try to skip loading that driver :-) > > I am sure that Jerome & Rugxulo can give better, informed answers. I have added a couple things to V8Power tools to remove the need for piping in the startup section of FDI. I’m currently working on Preview 13. Basically, a complete rewrite of the initialization an environment preparation for the installer. It is much more robust and is completely drive letter agnostic. > > "Guessful" regards, Eric > > PS: I suspected that LFN issue to be findfirst/findnext/findclose > related, but it could also be something totally different, such as > a bug in LFN support of command.com itself or in using LH w/o UMB. > > > > ------------------------------------------------------------------------------ > 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-user mailing list > Freedos-user@lists.sourceforge.net > https://lists.sourceforge.net/lists/listinfo/freedos-user > ------------------------------------------------------------------------------ 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-user mailing list Freedos-user@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/freedos-user
