Re: [Freedos-user] Cobalt - my FreeDOS distribution
When I clicked on the iso link, I got the following: This XML file does not appear to have any style information associated with it. The document tree is shown below. NoSuchKeyThe specified key does not exist.releases/50886493/4fb4d114-c933-11e5-9bf4-8e8a690fb98a.iso85117D7417E47724hJzwQuKFwih9sa3LSZ8nelMuDFPUBxxnwGSRhRlYlJWhqiSB2QDHTgorWNOaemkZ I'm running xubuntu 15.04 and Firefox 44.0 John -- 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
Re: [Freedos-user] FreeDOS 1.2 Preview 11
Hello Don, > On Feb 3, 2016, at 6:50 PM, Don Flowers wrote: > > It's the installed system - what was happening was > I would type: "COPY *.ZIP C:\DOWNLOAD\ZIP" > One file would copy to c:\download\zip, then the a: drive would click and I > got the ever annoying "error copying to a: drive abort retry ignore?"; I > could ignore and it would stop but the copy processed stopped as well. If I > repeat the process I get a clean copy of all files. > I solved the problem by rearranging the autoexec paths (FDAUTO for me :^) and > setting an absolute path for C:\;C:\FDOS;C:\FDOS\BIN > > > Interesting, if changing the chaning them path variable order fixed the issue. It would not be a bug or other issue in the installer. Thanks for the update. Jerome > > >> On Wed, Feb 3, 2016 at 5:21 PM, Jerome Shidel wrote: >> Hello Don, >> >> > On Feb 3, 2016, at 1:47 PM, Don Flowers wrote: >> > >> > Day after observation: I am getting an A: drive redirect when I try to >> > copy files by "COPY" command. One file will copy to the desired directory >> > and then it searches for the A: drive. Would this be a glitch from the >> > installer? >> > >> >> I'm not sure exactly what you mean. >> >> Is this the installed system, or when booted from floppy or USB image? >> >> Also, is this what you mean? >> >> cd c: >> copy myfile.txt fdos\myfile.txt >> copy myfile2.txt fdos\myfile2.txt >> INSERT DISK IN DRIVE A: >> >> Or do you mean something else entirely? >> >> Jerome >> >> Sent from my iPhone, ignore bad sentence structures, grammatical errors and >> incorrect spell-corrected words. >> >> >> -- >> 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 -- 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
Re: [Freedos-user] FreeDOS 1.2 Preview 11
It's the installed system - what was happening was I would type: "COPY *.ZIP C:\DOWNLOAD\ZIP" One file would copy to c:\download\zip, then the a: drive would click and I got the ever annoying "error copying to a: drive abort retry ignore?"; I could ignore and it would stop but the copy processed stopped as well. If I repeat the process I get a clean copy of all files. I solved the problem by rearranging the autoexec paths (FDAUTO for me :^) and setting an absolute path for C:\;C:\FDOS;C:\FDOS\BIN On Wed, Feb 3, 2016 at 5:21 PM, Jerome Shidel wrote: > Hello Don, > > > On Feb 3, 2016, at 1:47 PM, Don Flowers wrote: > > > > Day after observation: I am getting an A: drive redirect when I try to > copy files by "COPY" command. One file will copy to the desired directory > and then it searches for the A: drive. Would this be a glitch from the > installer? > > > > I'm not sure exactly what you mean. > > Is this the installed system, or when booted from floppy or USB image? > > Also, is this what you mean? > > cd c: > copy myfile.txt fdos\myfile.txt > copy myfile2.txt fdos\myfile2.txt > INSERT DISK IN DRIVE A: > > Or do you mean something else entirely? > > Jerome > > Sent from my iPhone, ignore bad sentence structures, grammatical errors > and incorrect spell-corrected words. > > > > -- > 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
Re: [Freedos-user] FreeDOS 1.2 Preview 11
Hello Don, > On Feb 3, 2016, at 1:47 PM, Don Flowers wrote: > > Day after observation: I am getting an A: drive redirect when I try to copy > files by "COPY" command. One file will copy to the desired directory and then > it searches for the A: drive. Would this be a glitch from the installer? > I'm not sure exactly what you mean. Is this the installed system, or when booted from floppy or USB image? Also, is this what you mean? cd c: copy myfile.txt fdos\myfile.txt copy myfile2.txt fdos\myfile2.txt INSERT DISK IN DRIVE A: Or do you mean something else entirely? Jerome Sent from my iPhone, ignore bad sentence structures, grammatical errors and incorrect spell-corrected words. -- 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
Re: [Freedos-user] Installation as standalone system
There is no need for sound, I don't think I even need a network connection. I'm looking to get a system that is at least 3-4 years old, maybe even older. The only reason to get a newer one is to get some extra speed. This clown speaks for himself > On Feb 3, 2016, at 1:33 PM, Corbin Davenport > wrote: > > I would think FreeDOS would work fine on any PC with legacy boot enabled, but > extra stuff like USB, sound, and/or networking might need extra drivers that > might not be available. > > Corbin > >> On Feb 3, 2016 12:57 PM, "Wayne Dernoncourt" wrote: >> I'm planning to install Free-DOS on a standalone system to run SpinRite. >> I've had issues in getting FreeDOS to boot successfully on some systems (the >> systems seems to hang on Init...) >> >> So I decided to get an older desktop with a plan to wipeout what I expect >> will be Windows and install FreeDOS. I would to minimize the number of >> systems I need to get before being successful at getting FreeDOS to boot, >> what are the characteristics I need to look for. >> >> BTW the Dell laptop I bought for this works pretty well, but I'm going to >> have problems mounting other desktop hard drives to the laptop that the >> desktop controller can deal with. As I understand things, USB limits the >> info coming back from the drive. >> >> This clown speaks for himself >> -- >> 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=267308311&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 -- 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
Re: [Freedos-user] FreeDOS 1.2 Preview 11
Day after observation: I am getting an A: drive redirect when I try to copy files by "COPY" command. One file will copy to the desired directory and then it searches for the A: drive. Would this be a glitch from the installer? On Tue, Feb 2, 2016 at 8:35 PM, Jerome E. Shidel Jr. wrote: > > > On Feb 2, 2016, at 7:54 PM, Eric Auer wrote: > > > > > > Hi! > > > >>> Well that is still serious. Even if you do something as harmless as > >>> > >>> copy STUFF SOMEWHERE | more > >>> > >>> you would still end up 1. not seeing the output of "copy" and > >>> possibly even 2. block the "copy" process by stalling the pipe. > >>> > >>> In short, please use a ramdisk for all your pipe and temp work :-) > >> > >> Yeah, probably not going to do that. It adds to much complication > >> to the installer startup. It would need to be very small and that > >> may risk package installation failure later on with fdinst. > > > > That is exactly why I recommend using a ramdisk: Without ramdisk, > > everything sent through pipes goes to a digital black hole when > > the install disk is not writeable, risking plenty of side effects. > > > > For piping stuff, a tiny ramdisk will be enough. If you assume that > > a computer which can boot from CD / DVD / USB has, say, at least 16 > > MB RAM (yes youngsters, not 16 GB ;-)) then you could use 4 for the > > cache and 1 for the ramdisk and have 10 left for installer / unzip > > 32 bit activities still. So a bit of a ramdisk is totally harmless! > > It really isn’t needed. > > > > > By the way, how about creating a 600 MB RAMDISK (no joke) whenever > > the installer detects 1 GB or more RAM? That would allow users to > > do a full install to the ramdisk, effectively using your installer > > stick as a "LIVE CD" without install and without rebooting :-) > > No reason, someone can not create an simple batch called something > like GOLIVE.BAT that could be included with the CD ISO. It could handle > all of that post-boot. Also, with how the installer is designed. A drop in > could even be included to do it when the user exits the installer without > performing an install. > > > > >> if a user did not boot the install media and just runs it from > >> the command line, a pre-existing ramdisk may cause issues or be > >> forcefully unloaded. It is also an additional driver to load. > > > > Ramdisks are pretty compatible and I see no reason why loading more > > than one of them would cause any troubles. Also, my suggestion was > > to load a ramdisk in CONFIG & AUTOEXEC. Everybody who manually wants > > to start the installer from the command line of their existing DOS > > or Windows can be expected to know what they do, so I agree to not > > bother those by loading DRIVERS as side effect of installer start. > > > > Maybe this is a good topic for review! As the moment, which steps > > do you take in CONFIG / AUTOEXEC and which steps, apart from the > > scripted invocation of (after optional fdisk and format) the DOS > > package manager and the creation of a target config and autoexec, > > are taken by the installer itself? Thanks for giving an overview! > > The entire installer is modular, customizable and extensible. > Other than at startup with language selection and initial target > verification, the installer performs no further actions until the > user makes the final “install now” selection. This with drop > in package lists, advanced mode, error handling screens and > all of the other steps it takes during execution. All logic is handled > inside the batch files that make up the installer. There is a rough > draft developer manual on the github source page that goes into > basic detail on what most of the different parts of the installer handle. > > > > >> There is an easy way around the issue. I will probably just have the > >> installer test if C: is the USB stick prior to activating the TEMP > >> directory. > > > > That will not work with PLOP, nor will it work with "booting from > > a harddisk image on CD or DVD", as those are all write-protected > > simulations of a C: harddisk as far as my intuition tells me that. > > Actually, the installer already does this in automatic target drive > detection. That is how it knows to install to D: automatically. But, > on some systems the USB drive is not C:, the installer automatically > targets C:. It shouldn’t be difficult to include some of this logic > into the initial (for settings import) TEMP directory setup. > > > > >> The batch file based FDI installer would not be very good without any > >> pipes. It would have almost no flexibility at all. Would only have > >> hard coded package lists and would not be able to dynamically > >> create customized system configuration files. > > > > You can do a lot with errorlevels and you can select packages AFTER > > selecting the target drive: By definition, as soon as the user has > > selected (and maybe formatted) a target drive, you can write it :-) > > Absolutely, but this is some of what you would
Re: [Freedos-user] Installation as standalone system
I would think FreeDOS would work fine on any PC with legacy boot enabled, but extra stuff like USB, sound, and/or networking might need extra drivers that might not be available. Corbin On Feb 3, 2016 12:57 PM, "Wayne Dernoncourt" wrote: > I'm planning to install Free-DOS on a standalone system to run SpinRite. > I've had issues in getting FreeDOS to boot successfully on some systems > (the systems seems to hang on Init...) > > So I decided to get an older desktop with a plan to wipeout what I expect > will be Windows and install FreeDOS. I would to minimize the number of > systems I need to get before being successful at getting FreeDOS to boot, > what are the characteristics I need to look for. > > BTW the Dell laptop I bought for this works pretty well, but I'm going to > have problems mounting other desktop hard drives to the laptop that the > desktop controller can deal with. As I understand things, USB limits the > info coming back from the drive. > > This clown speaks for himself > > -- > 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=267308311&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
[Freedos-user] Installation as standalone system
I'm planning to install Free-DOS on a standalone system to run SpinRite. I've had issues in getting FreeDOS to boot successfully on some systems (the systems seems to hang on Init...) So I decided to get an older desktop with a plan to wipeout what I expect will be Windows and install FreeDOS. I would to minimize the number of systems I need to get before being successful at getting FreeDOS to boot, what are the characteristics I need to look for. BTW the Dell laptop I bought for this works pretty well, but I'm going to have problems mounting other desktop hard drives to the laptop that the desktop controller can deal with. As I understand things, USB limits the info coming back from the drive. This clown speaks for himself -- 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=267308311&iu=/4140 ___ Freedos-user mailing list Freedos-user@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/freedos-user