Subj : Bluetooth Keyboard
To   : Ky Moffet
From : Barry Martin
Date : Thu Sep 19 2024 07:04:00



Hi Ky!


 >   > There's probably an option in the BIOS/UEFI to turn off something like
 >   > the initialization logo -- as I recall they call it different things.
 >   > The problem is now the test scrolls by too fast to read -- what was the
 >   > line with the red text I think said 'Failed'?
 >   > What would probably be a lot easier is to let the computer boot and
 >   > then look at the loggiing.  For Ubuntu it's usually in  /var/log/
 >   > (Linux uses forward slashes), though dmesg also can be helpful.  And
 >   > sometimes specific utilties will put their logs in a subdirectory of
 >   > /var/log and sometimes they feel special and create their own area.
 >   > You might want to copy any logs you're interested in to a ramdrive or
 >   > temporary directory: some logs are constantly being updated -- not sure
 >   > if "hard' on the logging to be staticly viewing while dynamically being
 >   > updated (written to).
 >
 >   EV> Documents and Settings create gobs of little bitty files.
 >   EV> It's a Jungle out there.
 >
 > <Visualizing Clippy wielding a machete, hacking through strings of text>
 >
 > Yes, and there's a small problem with that: the hard drive (OK: storage
 > media) is partitioned into blocks of certain sizes -- in the old-old
 > days 1024 bytes.  1023 bytes of data, great!  Use 1025, just used two
 > blocks and 99% of that second block is empty.  I've always stored a lot
 > of potentially useful information on my computer just so I could have it
 > handy.  With a 20 MB hard drive I wanted to maximize that capacity so
 > would spend time editing files to fit in that 1023 parameter. ...It
 > seemed to work, but probably in the long term not worth the time and
 > effort.  And of course now a TB of storage - no problem!
 KM> It's still 1024 bytes, or multiples thereof.
 
Once get a good thing may as well stick with it! <g>

 KM> NTFS filesystem stores very small files (less than one cluster)
 KM> in the file table rather than in separate clusters. Probably in
 KM> the same cluster as the filemane and other file information.

What, the File Allocation Table?!


 KM> Slack space is still a problem tho, can easily eat a good chunk
 KM> of a big drive. But less with NTFS than with FAT. And nowadays...
 KM> one terabyte more or less, who cares?
 
Right!  The unused space to available storgae is probably relatively 
small, though still greater than the capacities of the hard drives on my
original XTs.


                     ¯                                 ®
                      ¯  BarryMartin3@MyMetronet.NET  ®
                     ¯                                 ®


.... Beware docks made of hickory: when rains becomes a slippery hickory dock.
--- MultiMail/Win32 v0.47
 þ wcECHO 4.2 ÷ ILink: The Safe BBS þ Bettendorf, IA

--- QScan/PCB v1.20a / 01-0462
 * Origin: ILink: CFBBS | cfbbs.no-ip.com (454:1/1)

.