Re: [Freedos-user] Freedos 1.2 move, copy & xcopy
Hallo Herr Ralf Quint, am Montag, 25. November 2019 um 18:43 schrieben Sie: > On 11/25/2019 8:36 AM, TK Chia wrote: >>> One problem here is what I mentioned a lot of times in the past but >>> always got scoffed at is that these are highly technical apps but do not >>> have any proper technical documentation. And they are typical examples >>> of where "the documentation is in the source code" just doesn't work to >>> understand the inner workings, its limitations and hence being able to >>> fix and/or update the program. >> >> I see that Microsoft did publish a "Microsoft Extensible Firmware >> Initiative FAT32 File System Specification" --- it should give us a >> (better) idea of the requirements that dosfsck is working towards. > The existence of 3rd party technical specs is not the problem I am > referring to... Yes indeed. uncertainty of FAT32 specifications is (nad never was) a problem for chkdsk and friends. they have to to deal with a huge ways of possible problems. in practice, they will only check (and ideally even correct) a much smaller class of problems. And while it's possible to check for accordance to *some* specified details; it's hugely more difficult to implement a sensible solution. it's just engineering hours that are missing. >I ran freedos chkdsk and it said: >"fat32 not currently supported" all that said: why is nobody able to replace "fat32 not currently supported" by "fat32 not currently supported, please use DOSFSCK" or even (in 2019 we have made huge steps in artificial intelligence) run DOSFSCK automatically from CHKDSK. that's one of the reasons for open source, NO? Tom ___ Freedos-user mailing list Freedos-user@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/freedos-user
Re: [Freedos-user] Freedos 1.2 move, copy & xcopy
On 11/25/2019 8:36 AM, TK Chia wrote: Hello Ralf Quint, Will try to take a closer look a bit later this evening. One problem here is what I mentioned a lot of times in the past but always got scoffed at is that these are highly technical apps but do not have any proper technical documentation. And they are typical examples of where "the documentation is in the source code" just doesn't work to understand the inner workings, its limitations and hence being able to fix and/or update the program. I see that Microsoft did publish a "Microsoft Extensible Firmware Initiative FAT32 File System Specification" --- it should give us a (better) idea of the requirements that dosfsck is working towards. The existence of 3rd party technical specs is not the problem I am referring to... Ralf ___ Freedos-user mailing list Freedos-user@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/freedos-user
Re: [Freedos-user] Freedos 1.2 move, copy & xcopy
Hello Ralf Quint, Will try to take a closer look a bit later this evening. One problem here is what I mentioned a lot of times in the past but always got scoffed at is that these are highly technical apps but do not have any proper technical documentation. And they are typical examples of where "the documentation is in the source code" just doesn't work to understand the inner workings, its limitations and hence being able to fix and/or update the program. I see that Microsoft did publish a "Microsoft Extensible Firmware Initiative FAT32 File System Specification" --- it should give us a (better) idea of the requirements that dosfsck is working towards. Thank you! -- https://github.com/tkchia ___ Freedos-user mailing list Freedos-user@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/freedos-user
Re: [Freedos-user] Freedos 1.2 move, copy & xcopy
On 11/24/2019 2:41 PM, Jon Brase wrote:
To expand on why CHKDSK itself can't deal with FAT32, Freedos tries to
retain compatibility with quite a broad range of hardware, including
both any 8086 machines that anybody still has lying around, and modern
hardware. So CHKDSK has to be able to be able to work on 8086s. This
means that it can't depend on the availability of anything more than
640k of conventional RAM, which makes it difficult to deal with FAT32,
and such machines are unlikely to have disks big enough to need FAT32
anyway. Thus there is a separate tool, ported from Linux, to deal with
FAT32 on beefier machines (i.e, most hardware released since 1990 or so).
Microsoft didn't have this constraint when they released FAT32 with
Win95, as they'd already determined that Win95 would not run on
machines that old, so MS CHKDSK has been able to deal with FAT32 since
it was released.
There is no inherit reason as to why the FreeDOS chkdsk program would
not be able to deal with FAT32 in the same way as the plain DOS chkdsk
that came with Windows 95 ("DOS 7.0") was able to deal with it. It just
requires mainly the knowledge of all the pitfalls of FAT32 compared to
FAT12/16 of previous DOS versions.
Beside that, "MS-DOS 7.0" chkdsk also did only a very rudimentary check
on FAT32 partitions, depending on the issue it would encounter, you
would get the message to try and run Scandisk, which was a new tool that
was included starting with MS-DOS 6.00, and for which there isn't an
equivalent tool for FreeDOS...
Ralf
___
Freedos-user mailing list
Freedos-user@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/freedos-user
Re: [Freedos-user] Freedos 1.2 move, copy & xcopy
On 11/24/2019 2:31 PM, Eric Auer wrote: Hi Ralf and Dale, please check http://www.ibiblio.org/pub/micro/pc-stuff/freedos/files/distributions/1.2/repos/pkg-html/dosfsck.html to get an impression of dosfsck :-) While the DOS port is old, it does know about LFN long file names and even checks for their consistency, as far as I remember. I am aware that it is part of FreeDOS, but it is relatively old and it basically "knows about" long filenames but I remember there were some issues with it. It's probably +10 years ago (the newest source file included is from August 8th, 2007, some go back to 2003) and my current email archive of the various FreeDOS mailing lists go back only to 2013. Will try to take a closer look a bit later this evening. One problem here is what I mentioned a lot of times in the past but always got scoffed at is that these are highly technical apps but do not have any proper technical documentation. And they are typical examples of where "the documentation is in the source code" just doesn't work to understand the inner workings, its limitations and hence being able to fix and/or update the program. Ralf ___ Freedos-user mailing list Freedos-user@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/freedos-user
Re: [Freedos-user] Freedos 1.2 move, copy & xcopy
To expand on why CHKDSK itself can't deal with FAT32, Freedos tries to retain compatibility with quite a broad range of hardware, including both any 8086 machines that anybody still has lying around, and modern hardware. So CHKDSK has to be able to be able to work on 8086s. This means that it can't depend on the availability of anything more than 640k of conventional RAM, which makes it difficult to deal with FAT32, and such machines are unlikely to have disks big enough to need FAT32 anyway. Thus there is a separate tool, ported from Linux, to deal with FAT32 on beefier machines (i.e, most hardware released since 1990 or so). Microsoft didn't have this constraint when they released FAT32 with Win95, as they'd already determined that Win95 would not run on machines that old, so MS CHKDSK has been able to deal with FAT32 since it was released.___ Freedos-user mailing list Freedos-user@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/freedos-user
Re: [Freedos-user] Freedos 1.2 move, copy & xcopy
Hi Ralf and Dale, please check http://www.ibiblio.org/pub/micro/pc-stuff/freedos/files/distributions/1.2/repos/pkg-html/dosfsck.html to get an impression of dosfsck :-) While the DOS port is old, it does know about LFN long file names and even checks for their consistency, as far as I remember. Cheers, Eric ___ Freedos-user mailing list Freedos-user@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/freedos-user
Re: [Freedos-user] Freedos 1.2 move, copy & xcopy
On 11/24/2019 2:03 PM, Dale E Sterner wrote: So why didn't freedos keep dosfsck; it its better?. There isn't really anything to keep, it is a Linux program. And I recall that there were issues with at least the early attempts to port this Linux app to plain DOS IIRC, like causing corruption at least with long filenames. As mentioned, a proper chkdsk that supports FAT32 is a less than trivial upgrade, as FAT32 is much more complex than just updating the math... Ralf ___ Freedos-user mailing list Freedos-user@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/freedos-user
Re: [Freedos-user] Freedos 1.2 move, copy & xcopy
> So why didn't freedos keep dosfsck; it its better? Hm? I expect FreeDOS to ship with both, dosfsck and chkdsk! The former can do fat32, but the latter is more familiar classic DOS style, so both are good :-) Eric ___ Freedos-user mailing list Freedos-user@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/freedos-user
Re: [Freedos-user] Freedos 1.2 move, copy & xcopy
So why didn't freedos keep dosfsck; it its better?. cheers DS On Sun, 24 Nov 2019 22:48:22 +0100 Eric Auer writes: > > Hi Dale, > > FAT32 has too large metadata to be convenient > to handle for CHKDSK. Because of this, it is > only supported by DOSFSCK, which requires a > 386 or newer CPU and several MB of free RAM. > > It has been a while since DOSFSCK got ported > to DOS, but I think you will be fine with the > older version which FreeDOS is still using :-) > > Of course, if anybody feels like backporting > the newest DOSFSCK version (from the Linux > dosfstools) to DOS, I am happy to provide > a bit of advice and support. No time to do > the actual update myself any soon, sorry. > > Regards, Eric > > > ___ > Freedos-user mailing list > Freedos-user@lists.sourceforge.net > https://lists.sourceforge.net/lists/listinfo/freedos-user > ** >From Dale Sterner - MS organic chemistry http://pubs.acs.org/doi/abs/10.1021/jo00975a052 *** Sad News For Meghan Markle And Prince Harry track.volutrk.com http://thirdpartyoffers.juno.com/TGL3141/5ddafe353215a7e3418efst01duc ___ Freedos-user mailing list Freedos-user@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/freedos-user
Re: [Freedos-user] Freedos 1.2 move, copy & xcopy
On 11/24/2019 1:44 PM, Dale E Sterner wrote: Why would Freedos be using a chkdsk that doesn't work on fat32? Because nobody has bothered to enable chkdsk to (safely!) work with FAT32 partitions. And that is a much bigger task done properly than just updating a few numbers to run over a larger number of sectors. But feel free to provide that update to chkdsk to properly handle FAT32, there will likely be a lot of users that would appreciate it... :P An that doesn't explain lchk's report on line 16. I'm starting to wonder if freedos runs on fat32 but doesn't support it -that seems strange if its true. That file you wanted so badly is c:\tcl86r2\clock.tcl and its 152K not 1.5meg as I reported to you. There should be plenty of editors that can handle a 150KB text file. Not near any of my FreeDOS PCs right now, but the DFlat based editor should be able to handle that, at least that used to be one of the points to use a 32bit development environment for it in the first place... Ralf ___ Freedos-user mailing list Freedos-user@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/freedos-user
Re: [Freedos-user] Freedos 1.2 move, copy & xcopy
Hi Dale, FAT32 has too large metadata to be convenient to handle for CHKDSK. Because of this, it is only supported by DOSFSCK, which requires a 386 or newer CPU and several MB of free RAM. It has been a while since DOSFSCK got ported to DOS, but I think you will be fine with the older version which FreeDOS is still using :-) Of course, if anybody feels like backporting the newest DOSFSCK version (from the Linux dosfstools) to DOS, I am happy to provide a bit of advice and support. No time to do the actual update myself any soon, sorry. Regards, Eric ___ Freedos-user mailing list Freedos-user@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/freedos-user
Re: [Freedos-user] Freedos 1.2 move, copy & xcopy
Why would Freedos be using a chkdsk that doesn't work on fat32? An that doesn't explain lchk's report on line 16. I'm starting to wonder if freedos runs on fat32 but doesn't support it -that seems strange if its true. That file you wanted so badly is c:\tcl86r2\clock.tcl and its 152K not 1.5meg as I reported to you. cheers DS On Sun, 24 Nov 2019 15:55:51 -0500 dmccunney writes: > On Sun, Nov 24, 2019 at 3:49 PM Dale E Sterner > wrote: > > > > I ran freedos chkdsk and it said: > > "fat32 not currently supported" > > This was on FREEdos1.2. > > Also lchk said on line 16 of its report: > > "FAT32 compatible disk access disabled" > > This was on FREEdos1.2 running on 32 gig cf chip > > with an FAT32 format. > > I'm not happy with the word "disabled" > > Can you explain why it used the word "disabled" > > FAT32 is not supported in that version of CHKDSK in that variant of > FreeDOS. > > If FAT32 is not supported and CHKDSK *can't* work on a FAT32 volume, > what would you *expect* lchk to say? > > > cheers > > DS > __ > Dennis > > > ___ > Freedos-user mailing list > Freedos-user@lists.sourceforge.net > https://lists.sourceforge.net/lists/listinfo/freedos-user > ** >From Dale Sterner - MS organic chemistry http://pubs.acs.org/doi/abs/10.1021/jo00975a052 *** Do This Before Bed, Watch Your Belly Fat Melt Like Crazy floraspring.com http://thirdpartyoffers.juno.com/TGL3141/5ddaf9eb90e479ea2fcest01duc ___ Freedos-user mailing list Freedos-user@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/freedos-user
Re: [Freedos-user] Freedos 1.2 move, copy & xcopy
On Sun, Nov 24, 2019 at 3:49 PM Dale E Sterner wrote: > > I ran freedos chkdsk and it said: > "fat32 not currently supported" > This was on FREEdos1.2. > Also lchk said on line 16 of its report: > "FAT32 compatible disk access disabled" > This was on FREEdos1.2 running on 32 gig cf chip > with an FAT32 format. > I'm not happy with the word "disabled" > Can you explain why it used the word "disabled" FAT32 is not supported in that version of CHKDSK in that variant of FreeDOS. If FAT32 is not supported and CHKDSK *can't* work on a FAT32 volume, what would you *expect* lchk to say? > cheers > DS __ Dennis ___ Freedos-user mailing list Freedos-user@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/freedos-user
Re: [Freedos-user] Freedos 1.2 move, copy & xcopy
I ran freedos chkdsk and it said: "fat32 not currently supported" This was on FREEdos1.2. Also lchk said on line 16 of its report: "FAT32 compatible disk access disabled" This was on FREEdos1.2 running on 32 gig cf chip with an FAT32 format. I'm not happy with the word "disabled" Can you explain why it used the word "disabled" cheers DS On Thu, 21 Nov 2019 18:10:28 -0600 Rugxulo writes: > Hi again, > > On Tue, Nov 12, 2019 at 2:09 PM Dale E Sterner > wrote: > > > > I'm running FREEDOS 1.2 on a 32 gig cf chip which works > > just like an IDE harddrive. Only about 2 gigs of the chip is > > used, the rest is free space with a FAT 32 format. > > It could be some kind of obscure firmware bug. So maybe a flaw in > your > BIOS (HDD emulation of CF) or something specific to the CF itself. I > don't know, I can only guess. > > My Lenovo desktop (2011) was triple-booting for many years. My FAT32 > partition there was "only" 4 GB. I had no problems in FreeDOS. When > that hard disk started dying, I backed it up to (I think?) a 16 GB > Lexar jump drive. (I have an older 1 GB Kingston jump drive that > still > works perfectly, but that uses FAT16, which is inefficient.) I did > actually see some copy problems and errors (in FreeDOS: FreeCOM, > etc), > but I just halfway assumed it was a firmware bug and decided not to > mess with that jump drive for active use (only for rarely grabbing > backup files). > > It could also be a FreeCOM bug. Or something else entirely. Or some > combination of bugs. It could also be something to do with DOSLFN > (if > you have that loaded). I don't know, just stating the obvious here: > there's a lot of little pieces, and none of them are perfect. > > I did create (empty) FAT16 and FAT32 (.VHD) files for MetaDOS. Not > exhaustive, sizes can vary quite a bit, so there's a lot that can be > tested. So, in theory, some bugs should be reproducible, if anyone > wanted to try. I (barely) suspect that larger FAT32 drives haven't > been tested as much for FreeDOS, at least not exhaustively > (utilities > and whatnot). But it's also likely that the main bug here isn't in > FreeDOS. It's very hard to iron out every obscure bug, especially > with > so few testers and volunteers. FreeDOS works great but is not immune > to bugs. > > > ___ > Freedos-user mailing list > Freedos-user@lists.sourceforge.net > https://lists.sourceforge.net/lists/listinfo/freedos-user > ** >From Dale Sterner - MS organic chemistry http://pubs.acs.org/doi/abs/10.1021/jo00975a052 *** 74 Year Old Grandma Shocks Doctors: Forget Botox, Do This removethewrinkles.com http://thirdpartyoffers.juno.com/TGL3141/5ddaec562912e6c55521cst02duc ___ Freedos-user mailing list Freedos-user@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/freedos-user
Re: [Freedos-user] Freedos 1.2 move, copy & xcopy
Hi again, On Tue, Nov 12, 2019 at 2:09 PM Dale E Sterner wrote: > > I'm running FREEDOS 1.2 on a 32 gig cf chip which works > just like an IDE harddrive. Only about 2 gigs of the chip is > used, the rest is free space with a FAT 32 format. It could be some kind of obscure firmware bug. So maybe a flaw in your BIOS (HDD emulation of CF) or something specific to the CF itself. I don't know, I can only guess. My Lenovo desktop (2011) was triple-booting for many years. My FAT32 partition there was "only" 4 GB. I had no problems in FreeDOS. When that hard disk started dying, I backed it up to (I think?) a 16 GB Lexar jump drive. (I have an older 1 GB Kingston jump drive that still works perfectly, but that uses FAT16, which is inefficient.) I did actually see some copy problems and errors (in FreeDOS: FreeCOM, etc), but I just halfway assumed it was a firmware bug and decided not to mess with that jump drive for active use (only for rarely grabbing backup files). It could also be a FreeCOM bug. Or something else entirely. Or some combination of bugs. It could also be something to do with DOSLFN (if you have that loaded). I don't know, just stating the obvious here: there's a lot of little pieces, and none of them are perfect. I did create (empty) FAT16 and FAT32 (.VHD) files for MetaDOS. Not exhaustive, sizes can vary quite a bit, so there's a lot that can be tested. So, in theory, some bugs should be reproducible, if anyone wanted to try. I (barely) suspect that larger FAT32 drives haven't been tested as much for FreeDOS, at least not exhaustively (utilities and whatnot). But it's also likely that the main bug here isn't in FreeDOS. It's very hard to iron out every obscure bug, especially with so few testers and volunteers. FreeDOS works great but is not immune to bugs. ___ Freedos-user mailing list Freedos-user@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/freedos-user
Re: [Freedos-user] Freedos 1.2 move, copy & xcopy
Hi, On Wed, Nov 13, 2019 at 3:04 PM Dale E Sterner wrote: > > I used the mem command to check for freespace. > Currently I'm using PCdos 7.1; since it only works > on fat16 I'm running out of space fast. I've never directly used PC-DOS. It's no longer sold nor developed anymore, AFAIK, so you can't really find it as easily. They did (supposedly) add FAT32 support to later (unofficial?) releases, sometime after PC-DOS 2000. I think they discontinued it in 2003, but IBM's Server Scripting Toolkit (not sure of exact licensing terms) supposedly had some parts of it that did support FAT32. (There are several other DOSes, besides MS, with FAT32 support, too.) Having said that, this is a FreeDOS mailing list. So, obviously, "just use FreeDOS!" :-) But it may not be perfect (yet?). Patches (or reproducible bug reports) welcome. ___ Freedos-user mailing list Freedos-user@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/freedos-user
Re: [Freedos-user] Freedos 1.2 move, copy & xcopy
Hi, (sorry I'm late) On Wed, Nov 13, 2019 at 2:40 PM Eric Auer wrote: > > > I have 30 gigs of freespace. I have 2 gigs used out of 32 gigs. > > Only FAT32 aware software will be able to notice when > you have more than 2 GB of free disk space ;-) > > Would be interesting to know which software already > has support and which not. What did you use to check > for free disk space? Apart from MOVE? DJGPP utils (2.04 or newer, e.g. "current" 2.05) should work (N.B. 386+, obviously) ... as long as your kernel version is set to 7. (That's in reference to Win95, aka MS-DOS 7, where FAT32 originated, OSR2 or whatever.) They still have separate CoreUtils, though (FileUtils + TextUtils + ShellUtils), hence three .ZIPs in /current/v2gnu/ : fil41br2.zip, txt20br2.zip, shl2011br2.zip Other utils (e.g. MOVE) using older compilers (and older C libraries, i.e. libc) will probably not work quite as well (atop FAT32). If in doubt, use the DJGPP (File)utils: cp.exe, mv.exe, rm.exe, du.exe, df.exe * http://www.delorie.com/djgpp/getting.html ___ Freedos-user mailing list Freedos-user@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/freedos-user
Re: [Freedos-user] Freedos 1.2 move, copy & xcopy
Ah a man with a true sense of justice. cheers DS On Thu, 14 Nov 2019 06:29:53 +0100 Tom Ehlert writes: > > >I have 2gigs of drive space used. It seems that move for > >some reason thinks the drive is full. > > > > > >I tried the copy command today and it worked. I don't understand > it. > > as said before: unless you tell us the exact command that failed, > you are just > producing noise. > > COPY *.* NEW > > will work. > > COPY *.* NEW\*.* > > will not. you might have indeed a memory problem. > not the one that MEM reports, but the one between your ears. > > Tom > > > > > > > > > ___ > Freedos-user mailing list > Freedos-user@lists.sourceforge.net > https://lists.sourceforge.net/lists/listinfo/freedos-user > ** >From Dale Sterner - MS organic chemistry http://pubs.acs.org/doi/abs/10.1021/jo00975a052 *** Sad News For Meghan Markle And Prince Harry track.volutrk.com http://thirdpartyoffers.juno.com/TGL3141/5dcdac659d4912c657418st03duc ___ Freedos-user mailing list Freedos-user@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/freedos-user
Re: [Freedos-user] Freedos 1.2 move, copy & xcopy
I just picked the file at random because I think it had a button command in it. Every time I type button it says "can't find msg 1.6". I figure a written file would get it right without the error. So where can I find a dos version of FLTK. Sounds interesting. With your extenive knowledge I was sure you would know what msg 1.6 is. If you don't know who would. cheers DS On Wed, 13 Nov 2019 19:28:17 -0500 dmccunney writes: > On Wed, Nov 13, 2019 at 3:53 PM Dale E Sterner > wrote: > > > > I don't know if I still have the file; since it didn't work > > I may have erased it. I probablely did. > > I don't *care* if you still have the file. I just wanted to know > what > its *name* was, so I could look at it if I grabbed the DOS TCL > distribution. Is giving me the file name too difficult for you? > > > Do you know what msg 1.6 is? It keeps asking for it. > > If I had it then it might work. > > I have no idea what it is. I haven't looked. > > > TK is the only interesting part of TCL. > > TK is properly a separate package. TCL can use it to create GUIs, > but > does not require it. It has been incorporated into other things. > There is a PerlTK, for example. > > If all you are interested in is TK, look into the FLTK package used > to > create some DOS app GUIs. > > > I wonder if TCL/TK is related to TK solver. > > Possible. I don't know. > > > cheers > > DS > __ > Dennis > > > ___ > Freedos-user mailing list > Freedos-user@lists.sourceforge.net > https://lists.sourceforge.net/lists/listinfo/freedos-user > ** >From Dale Sterner - MS organic chemistry http://pubs.acs.org/doi/abs/10.1021/jo00975a052 *** Drink 1 Cup Before Bed, Watch Your Belly Fat Melt Like Crazy mayserve-magestor.com http://thirdpartyoffers.juno.com/TGL3141/5dcdab722d0b2b71240fst04duc ___ Freedos-user mailing list Freedos-user@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/freedos-user
Re: [Freedos-user] Freedos 1.2 move, copy & xcopy
I don't what happened to my copy command. Last try it worked It is just move now that has a problem. I think TCL loaded something that interfered with copy for awhile. I think "move" is affected by the 2 gigs I have loaded; it thinks the drive is full for some reason. cheers DS On Wed, 13 Nov 2019 17:40:09 -0600 Jim Hall writes: > On Wed, Nov 13, 2019 at 4:20 PM ZB wrote: > > > > On Wed, Nov 13, 2019 at 05:09:50PM -0500, Dale E Sterner wrote: > > > > > The different OS's all use the same ram. I just change the chip > > > then boot. One computer, many OS's. Just change the > > > chip - easy. If there were a problem, certainly one of > > > them would report it. > > > > OK - it's what _I_ would do just to be 100% sure. > > > > Obviously your problem doesn't seem to be FreeDOS-related. Most > probably > > it's the issue with (part of) hardware you're using > > -- > > I agree, this is probably specific to the setup. I am able to copy > large files (largest single file is 17MB) on FreeDOS, between > different drives (D: to C:) and between different directories > (C:\TEMP > to C:\TEMP\DIR2) and everything works fine. > > COPY and XCOPY both work fine here. > > I'm running FreeDOS 1.2 on QEMU. > > > Jim > > > ___ > Freedos-user mailing list > Freedos-user@lists.sourceforge.net > https://lists.sourceforge.net/lists/listinfo/freedos-user > ** >From Dale Sterner - MS organic chemistry http://pubs.acs.org/doi/abs/10.1021/jo00975a052 *** Hilarious Photo From Down South poplively.com http://thirdpartyoffers.juno.com/TGL3141/5dcda8589137528580771st01duc ___ Freedos-user mailing list Freedos-user@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/freedos-user
Re: [Freedos-user] Freedos 1.2 move, copy & xcopy
Anything is possible. cheers DS On Wed, 13 Nov 2019 23:17:08 +0100 ZB writes: > On Wed, Nov 13, 2019 at 05:09:50PM -0500, Dale E Sterner wrote: > > > The different OS's all use the same ram. I just change the chip > > then boot. One computer, many OS's. Just change the > > chip - easy. If there were a problem, certainly one of > > them would report it. > > OK - it's what _I_ would do just to be 100% sure. > > Obviously your problem doesn't seem to be FreeDOS-related. Most > probably > it's the issue with (part of) hardware you're using > -- > regards, > Zbigniew > > > ___ > Freedos-user mailing list > Freedos-user@lists.sourceforge.net > https://lists.sourceforge.net/lists/listinfo/freedos-user > ** >From Dale Sterner - MS organic chemistry http://pubs.acs.org/doi/abs/10.1021/jo00975a052 *** Sad News For Meghan Markle And Prince Harry track.volutrk.com http://thirdpartyoffers.juno.com/TGL3141/5dcda40f16ab4240e3dc4st02duc ___ Freedos-user mailing list Freedos-user@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/freedos-user
Re: [Freedos-user] Freedos 1.2 move, copy & xcopy
>I have 2gigs of drive space used. It seems that move for >some reason thinks the drive is full. > > >I tried the copy command today and it worked. I don't understand it. as said before: unless you tell us the exact command that failed, you are just producing noise. COPY *.* NEW will work. COPY *.* NEW\*.* will not. you might have indeed a memory problem. not the one that MEM reports, but the one between your ears. Tom ___ Freedos-user mailing list Freedos-user@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/freedos-user
Re: [Freedos-user] Freedos 1.2 move, copy & xcopy
On Wed, Nov 13, 2019 at 3:53 PM Dale E Sterner wrote: > > I don't know if I still have the file; since it didn't work > I may have erased it. I probablely did. I don't *care* if you still have the file. I just wanted to know what its *name* was, so I could look at it if I grabbed the DOS TCL distribution. Is giving me the file name too difficult for you? > Do you know what msg 1.6 is? It keeps asking for it. > If I had it then it might work. I have no idea what it is. I haven't looked. > TK is the only interesting part of TCL. TK is properly a separate package. TCL can use it to create GUIs, but does not require it. It has been incorporated into other things. There is a PerlTK, for example. If all you are interested in is TK, look into the FLTK package used to create some DOS app GUIs. > I wonder if TCL/TK is related to TK solver. Possible. I don't know. > cheers > DS __ Dennis ___ Freedos-user mailing list Freedos-user@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/freedos-user
Re: [Freedos-user] Freedos 1.2 move, copy & xcopy
On Wed, Nov 13, 2019 at 4:20 PM ZB wrote: > > On Wed, Nov 13, 2019 at 05:09:50PM -0500, Dale E Sterner wrote: > > > The different OS's all use the same ram. I just change the chip > > then boot. One computer, many OS's. Just change the > > chip - easy. If there were a problem, certainly one of > > them would report it. > > OK - it's what _I_ would do just to be 100% sure. > > Obviously your problem doesn't seem to be FreeDOS-related. Most probably > it's the issue with (part of) hardware you're using > -- I agree, this is probably specific to the setup. I am able to copy large files (largest single file is 17MB) on FreeDOS, between different drives (D: to C:) and between different directories (C:\TEMP to C:\TEMP\DIR2) and everything works fine. COPY and XCOPY both work fine here. I'm running FreeDOS 1.2 on QEMU. Jim ___ Freedos-user mailing list Freedos-user@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/freedos-user
Re: [Freedos-user] Freedos 1.2 move, copy & xcopy
On Wed, Nov 13, 2019 at 05:09:50PM -0500, Dale E Sterner wrote: > The different OS's all use the same ram. I just change the chip > then boot. One computer, many OS's. Just change the > chip - easy. If there were a problem, certainly one of > them would report it. OK - it's what _I_ would do just to be 100% sure. Obviously your problem doesn't seem to be FreeDOS-related. Most probably it's the issue with (part of) hardware you're using -- regards, Zbigniew ___ Freedos-user mailing list Freedos-user@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/freedos-user
Re: [Freedos-user] Freedos 1.2 move, copy & xcopy
The different OS's all use the same ram. I just change the chip then boot. One computer, many OS's. Just change the chip - easy. If there were a problem, certainly one of them would report it. Right now I'm using win 95, tomorrow it could be xp or me on the same machine that I run DOS on. I have at least 5 versions of dos that I run on this computer. PCdos is my favorite. cheers DS On Wed, 13 Nov 2019 22:47:06 +0100 ZB writes: > On Wed, Nov 13, 2019 at 04:46:43PM -0500, Dale E Sterner wrote: > > > I use cf chips and run many OS's. None are showing > > any problems. > > I meant RAM - not your Compact Flash "HDD replacement" > -- > regards, > Zbigniew > > > ___ > Freedos-user mailing list > Freedos-user@lists.sourceforge.net > https://lists.sourceforge.net/lists/listinfo/freedos-user > ** >From Dale Sterner - MS organic chemistry http://pubs.acs.org/doi/abs/10.1021/jo00975a052 *** Genius Creates Revolutionary "Bullseye Trading" System bullseyeoptiontrading.com http://thirdpartyoffers.juno.com/TGL3141/5dcc7f36348007f353e94st04duc ___ Freedos-user mailing list Freedos-user@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/freedos-user
Re: [Freedos-user] Freedos 1.2 move, copy & xcopy
On Wed, Nov 13, 2019 at 04:46:43PM -0500, Dale E Sterner wrote: > I use cf chips and run many OS's. None are showing > any problems. I meant RAM - not your Compact Flash "HDD replacement" -- regards, Zbigniew ___ Freedos-user mailing list Freedos-user@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/freedos-user
Re: [Freedos-user] Freedos 1.2 move, copy & xcopy
I use cf chips and run many OS's. None are showing any problems. cheers DS On Wed, 13 Nov 2019 22:37:15 +0100 ZB writes: > On Wed, Nov 13, 2019 at 04:33:07PM -0500, Dale E Sterner wrote: > > > I have 2gigs of drive space used. It seems that move for > > some reason thinks the drive is full. I tried the copy > > command today and it worked. I don't understand it. > > Maybe it's RAM-related issue? Faulty RAM may make programs > malfunctioning. > You may want to test your RAM using Memtest86+ from "Linux System > Rescue CD" > -- > regards, > Zbigniew > > > ___ > Freedos-user mailing list > Freedos-user@lists.sourceforge.net > https://lists.sourceforge.net/lists/listinfo/freedos-user > ** >From Dale Sterner - MS organic chemistry http://pubs.acs.org/doi/abs/10.1021/jo00975a052 *** Men, You Need To Try This ED Solution Immediately Med Journal http://thirdpartyoffers.juno.com/TGL3141/5dcc79babf16079ba286fst03duc ___ Freedos-user mailing list Freedos-user@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/freedos-user
Re: [Freedos-user] Freedos 1.2 move, copy & xcopy
I thought of that but everything on one partition would be better. Have you ever run into msg 1.6 which is what TCL8.69 keeps asking for. If it had it then it might run. cheers DS On Wed, 13 Nov 2019 16:22:55 -0500 dmccunney writes: > On Wed, Nov 13, 2019 at 4:04 PM Dale E Sterner > wrote: > > > > I used the mem command to check for freespace. > > Currently I'm using PCdos 7.1; since it only works > > on fat16 I'm running out of space fast. > > What you will have to do is partition your 32GB drive to break out > additional 2GB volumes. Assign drive letters an PCDOS should see > them > and let you copy or move files to them. > > Or switch to a different version of DOS. I had FreeDOS installed in > a > multiboot configuration on an old notebook, with Win2K Pro, two > flavors of Linux, and FreeDOS. I partitioned the drive. The Win2K > install got 20GB formatted NTFS, the Linux slices got 8GB each, > formatted ext4, and FreeDOS got a 2GB slice formatted FAT32. (The > remainder was for a swap partition used by Linux.) It had no > problem > with it being FAT32, and I could have given it a larger slice, but > nothing I would install or use under FreeDOS needed a larger volume. > > > cheers > > DS > __ > Dennis > > > ___ > Freedos-user mailing list > Freedos-user@lists.sourceforge.net > https://lists.sourceforge.net/lists/listinfo/freedos-user > ** >From Dale Sterner - MS organic chemistry http://pubs.acs.org/doi/abs/10.1021/jo00975a052 *** Flooding Begins From Tropical Storm Karen newsprecinct.com http://thirdpartyoffers.juno.com/TGL3141/5dcc79404d0fb79402f05st01duc ___ Freedos-user mailing list Freedos-user@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/freedos-user
Re: [Freedos-user] Freedos 1.2 move, copy & xcopy
On Wed, Nov 13, 2019 at 04:33:07PM -0500, Dale E Sterner wrote: > I have 2gigs of drive space used. It seems that move for > some reason thinks the drive is full. I tried the copy > command today and it worked. I don't understand it. Maybe it's RAM-related issue? Faulty RAM may make programs malfunctioning. You may want to test your RAM using Memtest86+ from "Linux System Rescue CD" -- regards, Zbigniew ___ Freedos-user mailing list Freedos-user@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/freedos-user
Re: [Freedos-user] Freedos 1.2 move, copy & xcopy
I have 2gigs of drive space used. It seems that move for some reason thinks the drive is full. I tried the copy command today and it worked. I don't understand it. cheers DS On Wed, 13 Nov 2019 22:07:45 +0100 ZB writes: > On Mon, Nov 11, 2019 at 10:01:37AM -0500, Dale E Sterner wrote: > > > Have you noticed that move, copy & xcopy refuse > > to work on files bigger than 3 meg. > > Just out of curiosity I created a ZIP archive of almost 4 MB size - > and > I don't see any problems with copy neither with move. I can > copy/move the > file on a whim. > > Maybe RAM size may be your issue? I don't know the way copy/move > works; > is it simply copying the file to memory first (as a whole) or "more > intelligent" way copying/moving it byte-by-byte from one to other > location. > > But I'm still using FreeDOS V1.0 > -- > regards, > Zbigniew > > > ___ > Freedos-user mailing list > Freedos-user@lists.sourceforge.net > https://lists.sourceforge.net/lists/listinfo/freedos-user > ** >From Dale Sterner - MS organic chemistry http://pubs.acs.org/doi/abs/10.1021/jo00975a052 *** Flooding Begins From Tropical Storm Karen newsprecinct.com http://thirdpartyoffers.juno.com/TGL3141/5dcc76de7b88776de329fst04duc ___ Freedos-user mailing list Freedos-user@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/freedos-user
Re: [Freedos-user] Freedos 1.2 move, copy & xcopy
On Wed, Nov 13, 2019 at 4:04 PM Dale E Sterner wrote: > > I used the mem command to check for freespace. > Currently I'm using PCdos 7.1; since it only works > on fat16 I'm running out of space fast. What you will have to do is partition your 32GB drive to break out additional 2GB volumes. Assign drive letters an PCDOS should see them and let you copy or move files to them. Or switch to a different version of DOS. I had FreeDOS installed in a multiboot configuration on an old notebook, with Win2K Pro, two flavors of Linux, and FreeDOS. I partitioned the drive. The Win2K install got 20GB formatted NTFS, the Linux slices got 8GB each, formatted ext4, and FreeDOS got a 2GB slice formatted FAT32. (The remainder was for a swap partition used by Linux.) It had no problem with it being FAT32, and I could have given it a larger slice, but nothing I would install or use under FreeDOS needed a larger volume. > cheers > DS __ Dennis ___ Freedos-user mailing list Freedos-user@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/freedos-user
Re: [Freedos-user] Freedos 1.2 move, copy & xcopy
On Mon, Nov 11, 2019 at 10:01:37AM -0500, Dale E Sterner wrote: > Have you noticed that move, copy & xcopy refuse > to work on files bigger than 3 meg. Just out of curiosity I created a ZIP archive of almost 4 MB size - and I don't see any problems with copy neither with move. I can copy/move the file on a whim. Maybe RAM size may be your issue? I don't know the way copy/move works; is it simply copying the file to memory first (as a whole) or "more intelligent" way copying/moving it byte-by-byte from one to other location. But I'm still using FreeDOS V1.0 -- regards, Zbigniew ___ Freedos-user mailing list Freedos-user@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/freedos-user
Re: [Freedos-user] Freedos 1.2 move, copy & xcopy
I 'm using fat32, the big plus for freedos. cheers DS On Wed, 13 Nov 2019 15:49:39 -0500 dmccunney writes: > On Wed, Nov 13, 2019 at 3:35 PM Dale E Sterner > wrote: > > > > Tried copy again and this time it worked - including wildcards. > > I've been running TCL for a week and maybe it did something > > it shouldn't have. Still had trouble with the move command; > > it comes back [Insufficient disk space in destination path] > > I have 30 gigs of freespace. I have 2 gigs used out of 32 gigs. > > Maybe it thinks 2 gigs is the limit for some reason? > > What file system is on your CF card? > > Remember that when DOS was first written, the maximum size of a > volume > *was* 2GB. > > That was a limitation of the FAT16 file system. The smallest unit of > disk DOS could address was the cluster. Each cluster needed a unique > address. 16 bit addressing meant a maximum of 65,536 unique cluster > addresses. The maximum size a cluster could be was imposed by the > FORMAT command, and was 32K. 65,536 x 32 = .2,097,152â¬, or a 2GB > volume. > > FAT32 was developed precisely to permit larger volumes as hard drives > got higher capacities. > > It sounds like something on your end thinks the volume size limit is > the FAT16 2GB, and isn't aware of the other 30GB. > > > DS > __ > Dennis > > > ___ > Freedos-user mailing list > Freedos-user@lists.sourceforge.net > https://lists.sourceforge.net/lists/listinfo/freedos-user ** >From Dale Sterner - MS organic chemistry http://pubs.acs.org/doi/abs/10.1021/jo00975a052 *** Forget Viagra: This Pill "Destroys" ED Without Prescription! Med Journal http://thirdpartyoffers.juno.com/TGL3141/5dcc7032817ac7032479est04duc ___ Freedos-user mailing list Freedos-user@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/freedos-user
Re: [Freedos-user] Freedos 1.2 move, copy & xcopy
> I don't know if I still have the file; since it didn't work > I may have erased it. I probablely did. > Do you know what msg 1.6 is? It keeps asking for it. > If I had it then it might work. > TK is the only interesting part of TCL. > I wonder if TCL/TK is related to TK solver. In the MOVE source code directory, I can do "grep 1.16 *.?" to find: move.c: error(1,16,"Insufficient disk space in destination path"); Apparently there is a bug in your local language translation of MOVE which makes it unable to show a translated sentence for "Insufficient disk space in destination path". If your question was about MOVE :-) You will have to have a NLS directory with NLSPATH pointing to it and a MOVE.* file for your LANG. For example MOVE.ES exists for Spanish users: 0.0:Move 0.1:Mueve un fichero/directorio a otro lugar. ... Eric ___ Freedos-user mailing list Freedos-user@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/freedos-user
Re: [Freedos-user] Freedos 1.2 move, copy & xcopy
I used the mem command to check for freespace. Currently I'm using PCdos 7.1; since it only works on fat16 I'm running out of space fast. cheers DS On Wed, 13 Nov 2019 21:39:33 +0100 Eric Auer writes: > > Hi Dale, > > > I have 30 gigs of freespace. I have 2 gigs used out of 32 gigs. > > Only FAT32 aware software will be able to notice when > you have more than 2 GB of free disk space ;-) > > Would be interesting to know which software already > has support and which not. What did you use to check > for free disk space? Apart from MOVE? > > Eric > > PS: Maybe TCL damaged some in-memory data of DOS and > made it believe to run out of memory soon after back > at the time when your COPY/XCOPY unexpectedly failed. > > > Tried copy again and this time it worked - including wildcards. > > > I've been running TCL for a week and maybe it did something > > it shouldn't have. Still had trouble with the move command; > > it comes back [Insufficient disk space in destination path] > > > I have 30 gigs of freespace. I have 2 gigs used out of 32 gigs. > > Maybe it thinks 2 gigs is the limit for some reason? > > > Mem shows 597K conventional free, 30K Upper 0 reserved > > 522,778K XMS, EMS is 32M. > > > Ver gave "FreeCom version 0.84-pre2 XMS Swap [Aug 28 2006 > 00:29:00] > > > I was very suprised to see the copy command work today. > > Right now I suspect TCL of changing something. > > > > ___ > Freedos-user mailing list > Freedos-user@lists.sourceforge.net > https://lists.sourceforge.net/lists/listinfo/freedos-user > ** >From Dale Sterner - MS organic chemistry http://pubs.acs.org/doi/abs/10.1021/jo00975a052 *** Forget Viagra: This Pill "Destroys" ED Without Prescription! Med Journal http://thirdpartyoffers.juno.com/TGL3141/5dcc6f7c3b926f7b11a0st01duc ___ Freedos-user mailing list Freedos-user@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/freedos-user
Re: [Freedos-user] Freedos 1.2 move, copy & xcopy
I don't know if I still have the file; since it didn't work I may have erased it. I probablely did. Do you know what msg 1.6 is? It keeps asking for it. If I had it then it might work. TK is the only interesting part of TCL. I wonder if TCL/TK is related to TK solver. cheers DS On Tue, 12 Nov 2019 16:12:26 -0500 dmccunney writes: > On Tue, Nov 12, 2019 at 4:07 PM Dale E Sterner > wrote: > > > > You can download TCL869 and play with it yourself. > > I wanted to know which specific example file you had a problem with. > How about actually answering the question? > > > Its dos but seems to need windows in the background. > > I wantn't to see what a radiobutton looked like. > > I believe the examples were professionally written > > a long time ago, now they're play toys. > > TK is a graphic toolkit that provides widgets you can display from > your code. No surprise if those things really need Windows of > Linux. > > You might want to look at the FLTK package being used for a few DOS > GUI apps as something usable under DOS. Getting the DOS port of TCL > to use FLTK can be a learning experience for you. > > > cheers > > DS > __ > Dennis > > > ___ > Freedos-user mailing list > Freedos-user@lists.sourceforge.net > https://lists.sourceforge.net/lists/listinfo/freedos-user > ** >From Dale Sterner - MS organic chemistry http://pubs.acs.org/doi/abs/10.1021/jo00975a052 *** Forget Viagra: This Pill "Destroys" ED Without Prescription! Med Journal http://thirdpartyoffers.juno.com/TGL3141/5dcc6cdd1e6fa6cdc576bst03duc ___ Freedos-user mailing list Freedos-user@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/freedos-user
Re: [Freedos-user] Freedos 1.2 move, copy & xcopy
On Wed, Nov 13, 2019 at 3:35 PM Dale E Sterner wrote: > > Tried copy again and this time it worked - including wildcards. > I've been running TCL for a week and maybe it did something > it shouldn't have. Still had trouble with the move command; > it comes back [Insufficient disk space in destination path] > I have 30 gigs of freespace. I have 2 gigs used out of 32 gigs. > Maybe it thinks 2 gigs is the limit for some reason? What file system is on your CF card? Remember that when DOS was first written, the maximum size of a volume *was* 2GB. That was a limitation of the FAT16 file system. The smallest unit of disk DOS could address was the cluster. Each cluster needed a unique address. 16 bit addressing meant a maximum of 65,536 unique cluster addresses. The maximum size a cluster could be was imposed by the FORMAT command, and was 32K. 65,536 x 32 = .2,097,152, or a 2GB volume. FAT32 was developed precisely to permit larger volumes as hard drives got higher capacities. It sounds like something on your end thinks the volume size limit is the FAT16 2GB, and isn't aware of the other 30GB. > DS __ Dennis ___ Freedos-user mailing list Freedos-user@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/freedos-user
Re: [Freedos-user] Freedos 1.2 move, copy & xcopy
Hi Dale, > I have 30 gigs of freespace. I have 2 gigs used out of 32 gigs. Only FAT32 aware software will be able to notice when you have more than 2 GB of free disk space ;-) Would be interesting to know which software already has support and which not. What did you use to check for free disk space? Apart from MOVE? Eric PS: Maybe TCL damaged some in-memory data of DOS and made it believe to run out of memory soon after back at the time when your COPY/XCOPY unexpectedly failed. > Tried copy again and this time it worked - including wildcards. > I've been running TCL for a week and maybe it did something > it shouldn't have. Still had trouble with the move command; > it comes back [Insufficient disk space in destination path] > I have 30 gigs of freespace. I have 2 gigs used out of 32 gigs. > Maybe it thinks 2 gigs is the limit for some reason? > Mem shows 597K conventional free, 30K Upper 0 reserved > 522,778K XMS, EMS is 32M. > Ver gave "FreeCom version 0.84-pre2 XMS Swap [Aug 28 2006 00:29:00] > I was very suprised to see the copy command work today. > Right now I suspect TCL of changing something. ___ Freedos-user mailing list Freedos-user@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/freedos-user
Re: [Freedos-user] Freedos 1.2 move, copy & xcopy
Tried copy again and this time it worked - including wildcards. I've been running TCL for a week and maybe it did something it shouldn't have. Still had trouble with the move command; it comes back [Insufficient disk space in destination path] I have 30 gigs of freespace. I have 2 gigs used out of 32 gigs. Maybe it thinks 2 gigs is the limit for some reason? Mem shows 597K conventional free, 30K Upper 0 reserved 522,778K XMS, EMS is 32M. Ver gave "FreeCom version 0.84-pre2 XMS Swap [Aug 28 2006 00:29:00] I was very suprised to see the copy command work today. Right now I suspect TCL of changing something. cheers DS On Tue, 12 Nov 2019 18:32:54 +0100 Eric Auer writes: > Hi Dale, > > > I tried to move post.mp4 - a 3.5.meg file. - got insufficient > memory > > error with move, copy & xcopy. > > Both should not have problems with files up to at least 2 GB > as long as you have enough free disk space. Please use MEM > to provide information about how much memory you have free > and of which type. > > > The copy command sometimes has trouble with wildcard "*". > > I tried copy *.* new\*.* It copied only > > one file then stopped,. xcopy worked. > > Please be more specific about the example and check which > command.com (FreeCOM, contains the COPY command) and which > FreeDOS kernel version you are using. > > > The edit command has limits on size; > > had to use Wordperfect on one file. In 2015 Dennis talked > > about using vedit but can't find a dos version. > > In the new world large files are common. > > Look at http://freedos.org/software/ which has a whole > section about editors included with FreeDOS: I think for > example SETEDIT can be used for really large files. > > Regards, Eric > > > > ___ > Freedos-user mailing list > Freedos-user@lists.sourceforge.net > https://lists.sourceforge.net/lists/listinfo/freedos-user > ** >From Dale Sterner - MS organic chemistry http://pubs.acs.org/doi/abs/10.1021/jo00975a052 *** Do This Before Bed, Watch Your Belly Fat Melt Like Crazy floraspring.com http://thirdpartyoffers.juno.com/TGL3141/5dcc68cff1f0168cf52d6st04duc ___ Freedos-user mailing list Freedos-user@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/freedos-user
Re: [Freedos-user] Freedos 1.2 move, copy & xcopy
> copy on MS-DOS wasn't really meant for copying more than one file > at a time bullshit. COPY can copy multiple files. both on MSDOS and FreeDOS. > (which is why xcopy exists), no. XCOPY /S is one of the reasons for it's existence. multiple files not. Tom ___ Freedos-user mailing list Freedos-user@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/freedos-user
Re: [Freedos-user] Freedos 1.2 move, copy & xcopy
Hallo Herr Dale E Sterner, am Dienstag, 12. November 2019 um 17:38 schrieben Sie: > I tried to move post.mp4 - a 3.5.meg file. - got insufficient memory > error with move, copy & xcopy. The copy command sometimes > has trouble with wildcard "*". I tried copy *.* new\*.* the correct command would be COPY *.* NEW (if new already exists) and XCOPY *.* NEW\ Tom ___ Freedos-user mailing list Freedos-user@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/freedos-user
Re: [Freedos-user] Freedos 1.2 move, copy & xcopy
On Tue, Nov 12, 2019 at 8:29 PM Thomas Mueller wrote: > From dmccunney: > > On Tue, Nov 12, 2019 at 11:40 AM Dale E Sterner wrote: > > > > The edit command has limits on size; had to use Wordperfect on one file. > > > In 2015 Dennis talked about using vedit but can't find a dos version. > > > In the new world large files are common. > > > Large files are common. Large *text* files are not. > > How large is a large text file? > 100 MB? Or more, or less. > One source of a large text file is the log file when compiling software. > Maybe this would occur more with Linux or BSD than FreeDOS. Things like /var/log in Linux systems can get enormous. But you normally don't need to *edit* them - just *view* them. Viewing is what things like less are for. > When rebuilding NetBSD from source, log file tends to exceed 100 MB; not so > huge with FreeBSD. > > I would usually not want to copy or edit such a file but might want to copy a > range of lines, for which I use vi, but this is not DOS. Under DOS, you are unlikely to need to. Under Linux or *BSD or Windows, you have the tools that can do it. And in any case, text files that large may *exist* in DOS, but *aren't* common. > Tom __ Dennis ___ Freedos-user mailing list Freedos-user@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/freedos-user
Re: [Freedos-user] Freedos 1.2 move, copy & xcopy
>From dmccunney: > On Tue, Nov 12, 2019 at 11:40 AM Dale E Sterner wrote: > > The edit command has limits on size; had to use Wordperfect on one file. > > In 2015 Dennis talked about using vedit but can't find a dos version. > > In the new world large files are common. > Large files are common. Large *text* files are not. How large is a large text file? > 100 MB? One source of a large text file is the log file when compiling software. Maybe this would occur more with Linux or BSD than FreeDOS. When rebuilding NetBSD from source, log file tends to exceed 100 MB; not so huge with FreeBSD. I would usually not want to copy or edit such a file but might want to copy a range of lines, for which I use vi, but this is not DOS. Tom ___ Freedos-user mailing list Freedos-user@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/freedos-user
Re: [Freedos-user] Freedos 1.2 move, copy & xcopy
xcopy came later, like MS-DOS 3.x or so. You can use copy for multiple files; it's just slower because it reads each file individually. I've used the copy command in MS DOS on 86box recently. Just to verify though I installed FreeDOS 1.2 on VirtualBox and I was able to copy fdos\bin\*.* to another directory just fine -using copy, not xcopy. Likewise I was able to create a zipfile out of fdos\bin\*.* and then copy the resulting archive (which was 5 megs) to another directory. This is using a stock installation. Default FreeCOM, default kernel. If the bug is referring to another version (of Freecom?) I'd be happy to try that instead. On Tuesday, November 12, 2019, 8:58:51 PM UTC, Dale E Sterner wrote: I'll have to try this on msdos 6.22 and pcdos 7.1. I'm sure I used this command to transfer files from floppies to a harddrive directory. a:\*.* c:\new\*.*. It shouldn't make any difference if A: is changed to c: Its been awhile.. cheers DS On Tue, 12 Nov 2019 14:36:11 -0600 Jon Brase writes: > copy on MS-DOS wasn't really meant for copying more than one file at > a time (which is why xcopy exists), and FreeDOS uses the same > command line syntax. Copy only accepts one destination file and > treats all other filenames on the command line as sources. Also, the > form new\*.* will expand to all the filenames *already in new*, if > any, so even if copy did take multiple destinations, throwing in > new\*.* for the destination would give you the results you expect > (it would overwrite existing files in new with copies of the source > files). > Long story short, Microsoft meant for you to use xcopy for what > you're trying to do back in the day, and FreeDOS is no different. > > Original message > From: Dale E Sterner > Date: 11/12/2019 10:38 (GMT-06:00) > To: freedos-user@lists.sourceforge.net > Subject: Re: [Freedos-user] Freedos 1.2 move, copy & xcopy > > I tried to move post.mp4 - a 3.5.meg file. - got insufficient memory > error with move, copy & xcopy. The copy command sometimes > has trouble with wildcard "*". I tried copy *.* new\*.* It copied > only > one file then stopped,. xcopy worked. The edit command has limits > on size; had to use Wordperfect on one file. In 2015 Dennis talked > about using vedit but can't find a dos version. > In the new world large files are common. > > > cheers > DS **>>>> >From Dale Sterner - MS organic chemistry http://pubs.acs.org/doi/abs/10.1021/jo00975a052 ***>>>> Simple Trick Is Improving Men's Love Lives Med Journal http://thirdpartyoffers.juno.com/TGL3141/5dcb1ca6abb31ca5577cst01duc ___ Freedos-user mailing list Freedos-user@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/freedos-user ___ Freedos-user mailing list Freedos-user@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/freedos-user
Re: [Freedos-user] Freedos 1.2 move, copy & xcopy
On Tue, Nov 12, 2019 at 4:07 PM Dale E Sterner wrote: > > You can download TCL869 and play with it yourself. I wanted to know which specific example file you had a problem with. How about actually answering the question? > Its dos but seems to need windows in the background. > I wantn't to see what a radiobutton looked like. > I believe the examples were professionally written > a long time ago, now they're play toys. TK is a graphic toolkit that provides widgets you can display from your code. No surprise if those things really need Windows of Linux. You might want to look at the FLTK package being used for a few DOS GUI apps as something usable under DOS. Getting the DOS port of TCL to use FLTK can be a learning experience for you. > cheers > DS __ Dennis ___ Freedos-user mailing list Freedos-user@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/freedos-user
Re: [Freedos-user] Freedos 1.2 move, copy & xcopy
You can download TCL869 and play with it yourself. Its dos but seems to need windows in the background. I wantn't to see what a radiobutton looked like. I believe the examples were professionally written a long time ago, now they're play toys. cheers DS On Tue, 12 Nov 2019 15:53:00 -0500 dmccunney writes: > On Tue, Nov 12, 2019 at 2:57 PM Dale E Sterner > wrote: > > > > I downloaded TCl 8.69 and have been playing with it. > > They give you TCL example files to run. One interesting > > file was about 1.5 meg. When I ran it, it would always > > ask for msg 1.6 (whatever that is) so I tried to edit the > > file to remove the part that made the error. The Freedos > > editor said it was too big so I used wordperfect to do it, > > which had zero problems doing it. Still got the message > > with that part removed. Tried TCL 8.5 also; its examples > > run wiithout the error but 8.5 doesn't have any of the TK > > commands like buttons. > > Which example file was this? TCL is an interpreted script language. > I am trying to imagine a TCL script language file that is 1.5MB in > size and failing. (You may well have one. I've just never seen one > that big.) > > WordPerfect will certainly have no problems - programs like that > assume large files and would have the coding to perform operations > on > data that spanned CPU segments. (You wouldn't fit a novel into 64K > of > text.) Text editors assumed program code as the source material, > and > programming tended to be modular. You didn't write one enormous > monolithic file. You broke your code up into modules that did > specific things, and the compiler would compile the modules and the > linker would put them together into an executable. If the source > code > for a program module exceeded 64K in size, you were arguably doing > it > wrong and needed to refactor your code. > > As mentioned, there are other DOS editors in the FreeDOS repo that > can > handle larger files. Even if you could find a DOS version of Vedit, > it would be *extreme* overkill. Vedit was notable because it could > successfully edit files from hundreds of megabytes up to 2 > *gigabytes* > in size. Most mere mortals will never need to do that. > > > cheers > > DS > __ > Dennis > > > ___ > Freedos-user mailing list > Freedos-user@lists.sourceforge.net > https://lists.sourceforge.net/lists/listinfo/freedos-user > ** >From Dale Sterner - MS organic chemistry http://pubs.acs.org/doi/abs/10.1021/jo00975a052 *** Meghan Markle Confirms Unfortunate News track.volutrk.com http://thirdpartyoffers.juno.com/TGL3141/5dcb1ecae25bc1eca76f6st03duc ___ Freedos-user mailing list Freedos-user@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/freedos-user
Re: [Freedos-user] Freedos 1.2 move, copy & xcopy
On 11/12/2019 12:36 PM, Jon Brase wrote: copy on MS-DOS wasn't really meant for copying more than one file at a time (which is why xcopy exists), and FreeDOS uses the same command line syntax. Copy only accepts one destination file and treats all other filenames on the command line as sources. Also, the form new\*.* will expand to all the filenames *already in new*, if any, so even if copy did take multiple destinations, throwing in new\*.* for the destination would give you the results you expect (it would overwrite existing files in new with copies of the source files). Long story short, Microsoft meant for you to use xcopy for what you're trying to do back in the day, and FreeDOS is no different. Sorry to be so blunt, but that is simply bollocks! The only difference between the intrinsic COPY command and the external XCOPY should be that the later should in most cases be faster due to using a larger buffer. You can copy any number of files, as long as you are staying within the limitations of the file system. Just as a quick test, I copied on my current FreeDOS 1.2 system (Dell Core 2 laptop with 60GB SSD) my folder with Ralf Brown's Interrupt List to a test folder. 94 files, for a total of 16MB, with the largest file a 5.5MB large combined INTERRUP.LST. All without a hitch. As for Dale's complain about editing large text files, that is in line with being compatible with MS/PC-DOS. Almost all editors had some hard limitations, EDIT AFAIR is limited to 64KB (max segment size), some others were limited to what's left of the base 640KB, Semware's QEDIT/TSE could handle up to 16MB when (sufficient) XMS memory was available and DeSmet C's SEE editor also can handle MB sized files by using spill files... My guess is that there is something else wrong with Dale's setup, with both hardware and software being possibilities... Ralf ___ Freedos-user mailing list Freedos-user@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/freedos-user
Re: [Freedos-user] Freedos 1.2 move, copy & xcopy
I'll have to try this on msdos 6.22 and pcdos 7.1. I'm sure I used this command to transfer files from floppies to a harddrive directory. a:\*.* c:\new\*.*. It shouldn't make any difference if A: is changed to c: Its been awhile.. cheers DS On Tue, 12 Nov 2019 14:36:11 -0600 Jon Brase writes: > copy on MS-DOS wasn't really meant for copying more than one file at > a time (which is why xcopy exists), and FreeDOS uses the same > command line syntax. Copy only accepts one destination file and > treats all other filenames on the command line as sources. Also, the > form new\*.* will expand to all the filenames *already in new*, if > any, so even if copy did take multiple destinations, throwing in > new\*.* for the destination would give you the results you expect > (it would overwrite existing files in new with copies of the source > files). > Long story short, Microsoft meant for you to use xcopy for what > you're trying to do back in the day, and FreeDOS is no different. > > Original message > From: Dale E Sterner > Date: 11/12/2019 10:38 (GMT-06:00) > To: freedos-user@lists.sourceforge.net > Subject: Re: [Freedos-user] Freedos 1.2 move, copy & xcopy > > I tried to move post.mp4 - a 3.5.meg file. - got insufficient memory > error with move, copy & xcopy. The copy command sometimes > has trouble with wildcard "*". I tried copy *.* new\*.* It copied > only > one file then stopped,. xcopy worked. The edit command has limits > on size; had to use Wordperfect on one file. In 2015 Dennis talked > about using vedit but can't find a dos version. > In the new world large files are common. > > > cheers > DS **>>>> >From Dale Sterner - MS organic chemistry http://pubs.acs.org/doi/abs/10.1021/jo00975a052 ***>>>> Simple Trick Is Improving Men's Love Lives Med Journal http://thirdpartyoffers.juno.com/TGL3141/5dcb1ca6abb31ca5577cst01duc ___ Freedos-user mailing list Freedos-user@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/freedos-user
Re: [Freedos-user] Freedos 1.2 move, copy & xcopy
On Tue, Nov 12, 2019 at 2:57 PM Dale E Sterner wrote: > > I downloaded TCl 8.69 and have been playing with it. > They give you TCL example files to run. One interesting > file was about 1.5 meg. When I ran it, it would always > ask for msg 1.6 (whatever that is) so I tried to edit the > file to remove the part that made the error. The Freedos > editor said it was too big so I used wordperfect to do it, > which had zero problems doing it. Still got the message > with that part removed. Tried TCL 8.5 also; its examples > run wiithout the error but 8.5 doesn't have any of the TK > commands like buttons. Which example file was this? TCL is an interpreted script language. I am trying to imagine a TCL script language file that is 1.5MB in size and failing. (You may well have one. I've just never seen one that big.) WordPerfect will certainly have no problems - programs like that assume large files and would have the coding to perform operations on data that spanned CPU segments. (You wouldn't fit a novel into 64K of text.) Text editors assumed program code as the source material, and programming tended to be modular. You didn't write one enormous monolithic file. You broke your code up into modules that did specific things, and the compiler would compile the modules and the linker would put them together into an executable. If the source code for a program module exceeded 64K in size, you were arguably doing it wrong and needed to refactor your code. As mentioned, there are other DOS editors in the FreeDOS repo that can handle larger files. Even if you could find a DOS version of Vedit, it would be *extreme* overkill. Vedit was notable because it could successfully edit files from hundreds of megabytes up to 2 *gigabytes* in size. Most mere mortals will never need to do that. > cheers > DS __ Dennis ___ Freedos-user mailing list Freedos-user@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/freedos-user
Re: [Freedos-user] Freedos 1.2 move, copy & xcopy
copy on MS-DOS wasn't really meant for copying more than one file at a time (which is why xcopy exists), and FreeDOS uses the same command line syntax. Copy only accepts one destination file and treats all other filenames on the command line as sources. Also, the form new\*.* will expand to all the filenames *already in new*, if any, so even if copy did take multiple destinations, throwing in new\*.* for the destination would give you the results you expect (it would overwrite existing files in new with copies of the source files). Long story short, Microsoft meant for you to use xcopy for what you're trying to do back in the day, and FreeDOS is no different. Original message From: Dale E Sterner Date: 11/12/2019 10:38 (GMT-06:00) To: freedos-user@lists.sourceforge.net Subject: Re: [Freedos-user] Freedos 1.2 move, copy & xcopy I tried to move post.mp4 - a 3.5.meg file. - got insufficient memory error with move, copy & xcopy. The copy command sometimes has trouble with wildcard "*". I tried copy *.* new\*.* It copied only one file then stopped,. xcopy worked. The edit command has limits on size; had to use Wordperfect on one file. In 2015 Dennis talked about using vedit but can't find a dos version. In the new world large files are common. cheers DS ___ Freedos-user mailing list Freedos-user@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/freedos-user
Re: [Freedos-user] Freedos 1.2 move, copy & xcopy
I'm running FREEDOS 1.2 on a 32 gig cf chip which works just like an IDE harddrive. Only about 2 gigs of the chip is used, the rest is free space with a FAT 32 format. I will check the things you mentioned. Thanks DS On Tue, 12 Nov 2019 18:32:54 +0100 Eric Auer writes: > Hi Dale, > > > I tried to move post.mp4 - a 3.5.meg file. - got insufficient > memory > > error with move, copy & xcopy. > > Both should not have problems with files up to at least 2 GB > as long as you have enough free disk space. Please use MEM > to provide information about how much memory you have free > and of which type. > > > The copy command sometimes has trouble with wildcard "*". > > I tried copy *.* new\*.* It copied only > > one file then stopped,. xcopy worked. > > Please be more specific about the example and check which > command.com (FreeCOM, contains the COPY command) and which > FreeDOS kernel version you are using. > > > The edit command has limits on size; > > had to use Wordperfect on one file. In 2015 Dennis talked > > about using vedit but can't find a dos version. > > In the new world large files are common. > > Look at http://freedos.org/software/ which has a whole > section about editors included with FreeDOS: I think for > example SETEDIT can be used for really large files. > > Regards, Eric > > > > ___ > Freedos-user mailing list > Freedos-user@lists.sourceforge.net > https://lists.sourceforge.net/lists/listinfo/freedos-user > ** >From Dale Sterner - MS organic chemistry http://pubs.acs.org/doi/abs/10.1021/jo00975a052 *** Men, Try This Tonight - You'll Never Need Viagra Again! com-show.news http://thirdpartyoffers.juno.com/TGL3141/5dcb10f87dc0b10f87bdfst03duc ___ Freedos-user mailing list Freedos-user@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/freedos-user
Re: [Freedos-user] Freedos 1.2 move, copy & xcopy
I downloaded TCl 8.69 and have been playing with it. They give you TCL example files to run. One interesting file was about 1.5 meg. When I ran it, it would always ask for msg 1.6 (whatever that is) so I tried to edit the file to remove the part that made the error. The Freedos editor said it was too big so I used wordperfect to do it, which had zero problems doing it. Still got the message with that part removed. Tried TCL 8.5 also; its examples run wiithout the error but 8.5 doesn't have any of the TK commands like buttons. cheers DS On Tue, 12 Nov 2019 13:26:09 -0500 dmccunney writes: > On Tue, Nov 12, 2019 at 11:40 AM Dale E Sterner > wrote: > > > The edit command has limits on size; had to use Wordperfect on > one file. > > In 2015 Dennis talked about using vedit but can't find a dos > version. > > In the new world large files are common. > > Large files are common. Large *text* files are not. > > DOS editors from back when typically had a 64K size limit on the > size > of a text file you could edit. (IIRC, Win3X versions of Windows > Notepad shared that limit.) This was related to Intel segmented > architecture. On the 8088 CPU used in the early PCs, a segment was > 64K. Text editors held the file you were editing in a segment, > assuming it was 64K or less in size. Handling larger files required > more complicated code to cross segment boundaries. Most folks > editing > plain text files were unlikely to deal with one larger than 64K, and > most text editors saw no need to handle larger text files. > > Just how big a file are you likely to need to edit? What sort of > file > is it, and why is it bigger than 64K? And for that matter, do you > need to *edit* it, or just *view* the contents? If you just need to > view a large file, you can look at something like the late Vern > Buerg's LIST, or Mark Nudelman's LESS command, which originated in > Unix and has a DOS port in the FreeDOS repository. Both should > handle > large files. > > Vedit was noted for being able to edit enormous files. The was at > one > point a DOS version, but I have no idea where it might be found now, > and you are extremely unlikely to need it. (If you *do*, you are > arguably doing it wrong.) > > As Eric Auer commented, Setedit should edit large files. So should > TDE. Both implemented cross segment addressing. > > > cheers > > DS > __ > Dennis > > > ___ > Freedos-user mailing list > Freedos-user@lists.sourceforge.net > https://lists.sourceforge.net/lists/listinfo/freedos-user > ** >From Dale Sterner - MS organic chemistry http://pubs.acs.org/doi/abs/10.1021/jo00975a052 *** $80K In Debt To 2.5 Million Trading Stocks ragingbull.com http://thirdpartyoffers.juno.com/TGL3141/5dcb0e598dab2e5957d5st01duc ___ Freedos-user mailing list Freedos-user@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/freedos-user
Re: [Freedos-user] Freedos 1.2 move, copy & xcopy
On Tue, Nov 12, 2019 at 11:40 AM Dale E Sterner wrote: > The edit command has limits on size; had to use Wordperfect on one file. > In 2015 Dennis talked about using vedit but can't find a dos version. > In the new world large files are common. Large files are common. Large *text* files are not. DOS editors from back when typically had a 64K size limit on the size of a text file you could edit. (IIRC, Win3X versions of Windows Notepad shared that limit.) This was related to Intel segmented architecture. On the 8088 CPU used in the early PCs, a segment was 64K. Text editors held the file you were editing in a segment, assuming it was 64K or less in size. Handling larger files required more complicated code to cross segment boundaries. Most folks editing plain text files were unlikely to deal with one larger than 64K, and most text editors saw no need to handle larger text files. Just how big a file are you likely to need to edit? What sort of file is it, and why is it bigger than 64K? And for that matter, do you need to *edit* it, or just *view* the contents? If you just need to view a large file, you can look at something like the late Vern Buerg's LIST, or Mark Nudelman's LESS command, which originated in Unix and has a DOS port in the FreeDOS repository. Both should handle large files. Vedit was noted for being able to edit enormous files. The was at one point a DOS version, but I have no idea where it might be found now, and you are extremely unlikely to need it. (If you *do*, you are arguably doing it wrong.) As Eric Auer commented, Setedit should edit large files. So should TDE. Both implemented cross segment addressing. > cheers > DS __ Dennis ___ Freedos-user mailing list Freedos-user@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/freedos-user
Re: [Freedos-user] Freedos 1.2 move, copy & xcopy
Hi Dale, > I tried to move post.mp4 - a 3.5.meg file. - got insufficient memory > error with move, copy & xcopy. Both should not have problems with files up to at least 2 GB as long as you have enough free disk space. Please use MEM to provide information about how much memory you have free and of which type. > The copy command sometimes has trouble with wildcard "*". > I tried copy *.* new\*.* It copied only > one file then stopped,. xcopy worked. Please be more specific about the example and check which command.com (FreeCOM, contains the COPY command) and which FreeDOS kernel version you are using. > The edit command has limits on size; > had to use Wordperfect on one file. In 2015 Dennis talked > about using vedit but can't find a dos version. > In the new world large files are common. Look at http://freedos.org/software/ which has a whole section about editors included with FreeDOS: I think for example SETEDIT can be used for really large files. Regards, Eric ___ Freedos-user mailing list Freedos-user@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/freedos-user
Re: [Freedos-user] Freedos 1.2 move, copy & xcopy
I tried to move post.mp4 - a 3.5.meg file. - got insufficient memory error with move, copy & xcopy. The copy command sometimes has trouble with wildcard "*". I tried copy *.* new\*.* It copied only one file then stopped,. xcopy worked. The edit command has limits on size; had to use Wordperfect on one file. In 2015 Dennis talked about using vedit but can't find a dos version. In the new world large files are common. cheers DS On Mon, 11 Nov 2019 18:03:20 +0100 Tom Ehlert writes: > > > Have you noticed that move, copy & xcopy refuse > > to work on files bigger than 3 meg. > No. And it's extremely unlikely that copy & xcopy fail in similar > ways (they are entirely unrelated). > > > > > I tried to relocate > > an mp4 file and they all said "out of memory" or > > was it "disk space"; > it would be helpful to SPELL OUT EXACTLY WHAT YOU DID and > WHAT THEY SAID. both copy, xcopy and move. > > > > anyway I couldn't relocate it. > > The copy command has trouble using wildcards > > but xcopy doesn't. > again: your bug reports are less then helpful. > > > > I hope that improves on version > > 1.3. > very unlikely. 1.3 changes the setup procedure; not much else. > > the last changes to COMMAND.COM were 13 years back. > > we have a documented (REN hurts) bug, have a fix for this (increase > stack size), and still no public binary 12 months later. > looks like bug fixing stalled ~2005. > > and given the quality of your bug reports: allow for some more > years. > > Tom > > > > ___ > Freedos-user mailing list > Freedos-user@lists.sourceforge.net > https://lists.sourceforge.net/lists/listinfo/freedos-user > ** >From Dale Sterner - MS organic chemistry http://pubs.acs.org/doi/abs/10.1021/jo00975a052 *** Meghan Markle Confirms Unfortunate News track.volutrk.com http://thirdpartyoffers.juno.com/TGL3141/5dcae01f8bfbb601f69f5st03duc ___ Freedos-user mailing list Freedos-user@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/freedos-user
Re: [Freedos-user] Freedos 1.2 move, copy & xcopy
> Have you noticed that move, copy & xcopy refuse > to work on files bigger than 3 meg. No. And it's extremely unlikely that copy & xcopy fail in similar ways (they are entirely unrelated). > I tried to relocate > an mp4 file and they all said "out of memory" or > was it "disk space"; it would be helpful to SPELL OUT EXACTLY WHAT YOU DID and WHAT THEY SAID. both copy, xcopy and move. > anyway I couldn't relocate it. > The copy command has trouble using wildcards > but xcopy doesn't. again: your bug reports are less then helpful. > I hope that improves on version > 1.3. very unlikely. 1.3 changes the setup procedure; not much else. the last changes to COMMAND.COM were 13 years back. we have a documented (REN hurts) bug, have a fix for this (increase stack size), and still no public binary 12 months later. looks like bug fixing stalled ~2005. and given the quality of your bug reports: allow for some more years. Tom ___ Freedos-user mailing list Freedos-user@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/freedos-user
[Freedos-user] Freedos 1.2 move, copy & xcopy
Have you noticed that move, copy & xcopy refuse to work on files bigger than 3 meg. I tried to relocate an mp4 file and they all said "out of memory" or was it "disk space"; anyway I couldn't relocate it. The copy command has trouble using wildcards but xcopy doesn't. I hope that improves on version 1.3. cheers DS ** >From Dale Sterner - MS organic chemistry http://pubs.acs.org/doi/abs/10.1021/jo00975a052 *** Drink 1 Cup Before Bed, Watch Your Body Fat Melt Like Crazy mayserve-magestor.com http://thirdpartyoffers.juno.com/TGL3141/5dc978154e2bb78153e6dst03duc ___ Freedos-user mailing list Freedos-user@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/freedos-user
