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 do
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.
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
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 abl
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
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 ca
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.
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 a
> 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
Free
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 a
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
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 w
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
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
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 wh
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
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 ca
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 al
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.
>
>
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
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 20
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 the
>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.
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
dis
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
> >
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 jus
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 a
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-use
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
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:
> >
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 malf
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:
>
> > H
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
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
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 so
> 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 sou
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.
>
> On
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 2
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 destinat
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
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
> 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
__
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
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
>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
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
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 w
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 dmccun
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.
rce
> 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-u
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 re
o 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
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 tri
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 t
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 no
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 o
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
> 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
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 versio
59 matches
Mail list logo
