From: "Glenn Ervin" <GlennErvin@cableone.net>
To: "Speakup is a screen review system for Linux." <speakup@braille.uwo.ca>
Subject: Re: A computer issue, how should I deal with this? Best solution?
Date: Sat, 23 Jun 2007 09:35:53 -0500 [thread overview]
Message-ID: <167c01c7b5a3$ce0e9f70$b100a8c0@AveratecLaptop> (raw)
In-Reply-To: <Pine.BSF.4.64.0706230718540.11431@server2.shellworld.net>
Butch, I agree
I think FAT32 is the only way to go with XP, and I think it would be easier
for Linux to access it,
as with DOS. NTFS does have larger clusters, and therefore wastes less
space on storing files, but with the difference as minor as it is, compared
to the size of drives, I see the trade-off of using FAT32 very worth it.
Sure NTFS is more secure, but on home systems, with firewalls & all, how
many of us need to worry about that anyway.
Glenn
----- Original Message -----
From: "Butch Bussen" <butchb@shellworld.net>
To: "Speakup is a screen review system for Linux." <speakup@braille.uwo.ca>
Sent: Saturday, June 23, 2007 9:22 AM
Subject: Re: A computer issue, how should I deal with this? Best solution?
I think we're confusing fat 16 and fat 32. The 2 gig limit applies for
fat 16, but when you run fdisk at the dos prompt, it says something like
"your computer system can support a hard disk larger than-----" "Do you
want to access this larger disk?"
It is before coffee and way too early in the morning for me to try and
figure out how they do it. I don't recall the numbers, I remember
discussing this stuff years ago on cluster size. That is the smallest
amount of space a file would take no matter if it were a one byte file.
I think it started out at 2 then 4 then 8 then 16 then 32.
Way to early to figure this out!!!
73s
Butch Bussen
wa0vjr
_______________________________________________
Speakup mailing list
Speakup@braille.uwo.ca
http://speech.braille.uwo.ca/mailman/listinfo/speakup
next prev parent reply other threads:[~ UTC|newest]
Thread overview: 30+ messages / expand[flat|nested] mbox.gz Atom feed top
Keith Hinton
` Willem van der Walt
` Doug Sutherland
` Gregory Nowak
` Glenn Ervin
` Gregory Nowak
` Gregory Nowak
` Butch Bussen
` Doug Sutherland
` Gaijin
` Butch Bussen
` Glenn Ervin
` Doug Sutherland
` Glenn Ervin
` Doug Sutherland
` Glenn Ervin
` Doug Sutherland
` Butch Bussen
` Glenn Ervin [this message]
` Doug Sutherland
` Steve Holmes
` Doug Sutherland
` Glenn Ervin
` Gregory Nowak
` Glenn Ervin
` Gregory Nowak
` Butch Bussen
` Butch Bussen
` John Heim
` Gaijin
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to='167c01c7b5a3$ce0e9f70$b100a8c0@AveratecLaptop' \
--to=glennervin@cableone.net \
--cc=speakup@braille.uwo.ca \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).