UPPERCASE always from other units
a
I have two (or to better say more) harddisk
on one of them I have w98
on another I have wxp sp2
when I boot on xp
the files on the xp harddisk
in Explorer are correctly shown in lower case
when I boot on w98
the same files on the xp harddisk
in Explorer are always shown in uppercase
if their name is up to 8 char long
note:
if the name is longer, eg: 12 char , it is shown in
lower case
note
the files on the w98 same harddisk are always shown correctly
How can I get the original lowercase filename
from onther harddisk (or pen drive)
correctly displayed in W98?
Tim Slattery
>How can I get the original lowercase filename
>from onther harddisk (or pen drive)
>correctly displayed in W98?
I don't a Win98 machine in front of me to check this out, but I'd
start by checking View|Folder Options, View tab in Windows Explorer.
See if any of the options listed there might help out.
--
Tim Slattery
MS MVP(DTS)
Slatt...@bls.gov
http://members.cox.net/slatteryt
BD
> a <a...@libero.it> wrote:
>
>> How can I get the original lowercase filename
>>from onther harddisk (or pen drive)
>> correctly displayed in W98?
>
> I don't a Win98 machine in front of me to check this out, but I'd
> start by checking View|Folder Options, View tab in Windows Explorer.
> See if any of the options listed there might help out.
>
IIRC in Folder Options there is a setting to allow/disallow folder names
in upper case.
PCR
That's right-- "START button, Settings, Folder Options, View tab".
I am checked there to "Allow all uppercase names". Here is the blurb for
that box...
"Specifies that your computer can display a file name in all uppercase
characters (such as FILENAME.TXT), if that’s the way the file name was
originally typed. When this option is not selected, file names are
changed to lowercase characters (such as Filename.txt), regardless of
how you typed them."
--
Thanks or Good Luck,
There may be humor in this post, and,
Naturally, you will not sue,
Should things get worse after this,
PCR
pcr...@netzero.net
Roxana
It's very annoying, as what are all lowercase in W98se, somehow later get to
be entirely uppercase - including the file extension - when examined in
W98se at some later time.... doubtless, after I've opened the folder or
files in XPsp2.
At any rate, the "solution" offered - eg - to disallow uppercase 'folder
names' is unsatifactory (for me) as I do wish some folder names - but not
necessarily *files* - to be in uppercase.
Maybe this might not happen if one "hid" each respective OS from the other ?
Maybe it's a vexing -never to go away problem -, only resolved by constant
application of a bulk renaming utility. lol :-/
"a" wrote in message news:2em9h35hjknpueoeb...@4ax.com...
a
wrote:
>a <a...@libero.it> wrote:
>
>>How can I get the original lowercase filename
>>from onther harddisk (or pen drive)
>>correctly displayed in W98?
>
>I don't a Win98 machine in front of me to check this out, but I'd
>start by checking View|Folder Options, View tab in Windows Explorer.
>See if any of the options listed there might help out.
no, no, no, the situation is different
(and your hint didn't work, and it couldn't)
I log in XP
I create a file with Notepad
I save it on XP harddisk
I name it "hallo.txt"
then
I log in w98
I fire Explorer.exe
I browse until I find the the previously created file on the XP harddisk
it is displayed as "Hallo.txt"
I'm very disappointed because
I develop web site on xp (many and many pages);
I Ftp them from W98 (their initial letteres are Uppercase as said);
My web site refuse them because in doesn't accept
filename with first lettter in Uppercase.
Franc Zabkar
keyboard and composed:
I'd use a disk editor to look at the actual directory entries for the
problem files. At the moment I don't it's possible to say whether the
problem is at the XP or W98 end.
What I would do is format a floppy diskette without putting a system
on it, and then use Win XP's Notepad to write one file to it. Then use
the DOS Debug command in a DOS box to dump the first sector of the
root directory (see below). This may tell you where the case change is
occurring.
debug
-L 100 0 13 1
-D 100
-Q
- Franc Zabkar
--
Please remove one 'i' from my address when replying by email.
PCR
| On Tue, 16 Oct 2007 12:26:44 -0400, Tim Slattery <Slatt...@bls.gov>
| wrote:
|
|>a <a...@libero.it> wrote:
|>
|>>How can I get the original lowercase filename
|>>from onther harddisk (or pen drive)
|>>correctly displayed in W98?
|>
|>I don't a Win98 machine in front of me to check this out, but I'd
|>start by checking View|Folder Options, View tab in Windows Explorer.
|>See if any of the options listed there might help out.
|
| no, no, no, the situation is different
| (and your hint didn't work, and it couldn't)
|
| I log in XP
| I create a file with Notepad
| I save it on XP harddisk
| I name it "hallo.txt"
|
| then
|
| I log in w98
| I fire Explorer.exe
| I browse until I find the the previously created file on the XP
| harddisk it is displayed as "Hallo.txt"
That is exactly what would happen-- IF you are unchecked to "Allow all
uppercase names" at "START button, Settings, Folder Options, View tab".
Explorer pretties up the DISPLAY of the name, by capitalizing the first
character & setting the others to be lower case. (But it doesn't
actually change the name itself.) Here is the blurb again, saying what
happens-- if you put a check in the box...
"Specifies that your computer can display a file name in all uppercase
characters (such as FILENAME.TXT), if that’s the way the file name was
originally typed. When this option is not selected, file names are
changed to lowercase characters (such as Filename.txt), regardless of
how you typed them."
You SHOULD put the check into that box! Then, Explorer will show the
actual name, unchanged-- capitals & lower case, whatever is really
there!
| I'm very disappointed because
| I develop web site on xp (many and many pages);
| I Ftp them from W98 (their initial letteres are Uppercase as said);
| My web site refuse them because in doesn't accept
| filename with first lettter in Uppercase.
--
PCR
| I've seen similar activity from my near identical setup such as yours
| is. It's very annoying, as what are all lowercase in W98se, somehow
| later get to be entirely uppercase - including the file extension -
| when examined in W98se at some later time.... doubtless, after I've
| opened the folder or files in XPsp2.
I'm not surprised to hear XP-irradiation could do that!
| At any rate, the "solution" offered - eg - to disallow uppercase
| 'folder names' is unsatifactory (for me) as I do wish some folder
| names - but not necessarily *files* - to be in uppercase.
That option in Win98 to "Allow all uppercase names", if checked,
actually allows both upper & lower case letters to show up-- whatever
the name really is! If the option is unchecked-- only the DISPLAY of the
name in Explorer is affected (not its actual spelling). Then, the first
letter shows up capitalized, & the rest lower-case.
SO... it's up to you to spell them right in the first place-- & to keep
them away from XP!
| Maybe this might not happen if one "hid" each respective OS from the
| other ?
If XP-irradiation is really doing it, then, YEA-- NEVER allow XP to see
that partition!
| Maybe it's a vexing -never to go away problem -, only
| resolved by constant application of a bulk renaming utility. lol :-/
Yea. If you want the original Windows folders & files to actually be
spelled differently, you must do it yourself or find something like
that.
|
| "a" wrote in message
| news:2em9h35hjknpueoeb...@4ax.com...
|> hallo
|>
|> I have two (or to better say more) harddisk
|>
|> on one of them I have w98
|> on another I have wxp sp2
|>
|> when I boot on xp
|> the files on the xp harddisk
|> in Explorer are correctly shown in lower case
|>
|> when I boot on w98
|> the same files on the xp harddisk
|> in Explorer are always shown in uppercase
|> if their name is up to 8 char long
|> note:
|> if the name is longer, eg: 12 char , it is shown in
|> lower case
|> note
|> the files on the w98 same harddisk are always shown correctly
|>
|>
|> How can I get the original lowercase filename
|> from onther harddisk (or pen drive)
|> correctly displayed in W98?
--
Roxana
"PCR" wrote in message news:ubMnhURE...@TK2MSFTNGP03.phx.gbl...
> Roxana wrote:
> | I've seen similar activity from my near identical setup such as yours
> | is. It's very annoying, as what are all lowercase in W98se, somehow
> | later get to be entirely uppercase - including the file extension -
> | when examined in W98se at some later time.... doubtless, after I've
> | opened the folder or files in XPsp2.
>
> I'm not surprised to hear XP-irradiation could do that!
Yes, it appears it does that.... and more ! (not LOL) . But for now, let me
be specific (as I was less than exact) in what I'm referring to.For example,
I have files created in - and initially displayed in - W98se as:
Blabla.txt
Whatever pic.jpg
File1009.jpg
Then, after some back and forth between XP-radiation's-ville and W98se
fallout shelter, I will then see in W98se (in Explorer/ some folder/
whatever):
BLABLA.TXT
WHATEVER PIC.JPG
FILE1009.JPG
>
> | At any rate, the "solution" offered - eg - to disallow uppercase
> | 'folder names' is unsatifactory (for me) as I do wish some folder
> | names - but not necessarily *files* - to be in uppercase.
>
> That option in Win98 to "Allow all uppercase names", if checked,
> actually allows both upper & lower case letters to show up-- whatever
> the name really is! If the option is unchecked-- only the DISPLAY of the
> name in Explorer is affected (not its actual spelling). Then, the first
> letter shows up capitalized, & the rest lower-case.
>
> SO... it's up to you to spell them right in the first place-- & to keep
> them away from XP!
I try the former, and as for the latter: If W98se were still attended to
with the reverence and care it deserves (from MS and software vendors and
the like), I'd never venture into that Three-mile Island XP region for even
one second. But alas.......
>
> | Maybe this might not happen if one "hid" each respective OS from the
> | other ?
>
> If XP-irradiation is really doing it, then, YEA-- NEVER allow XP to see
> that partition!
Then I must make everything that I might be able to access in W98se
*invisible* to XP ? (I'm always trying to avoid any *System* related things
already). Do you mean that even looking at 98se data from XP can be bad ?
(I'm not talking about running 98se programs within XP).
> | Maybe it's a vexing -never to go away problem -, only
> | resolved by constant application of a bulk renaming utility. lol :-/
>
> Yea. If you want the original Windows folders & files to actually be
> spelled differently, you must do it yourself or find something like
> that.
Which is what I've had to do on more than one occasion. :-/
PCR
| "PCR" wrote in message news:ubMnhURE...@TK2MSFTNGP03.phx.gbl...
|> Roxana wrote:
|> | I've seen similar activity from my near identical setup such as
|> | yours is. It's very annoying, as what are all lowercase in W98se,
|> | somehow later get to be entirely uppercase - including the file
|> | extension - when examined in W98se at some later time....
|> | doubtless, after I've opened the folder or files in XPsp2.
|>
|> I'm not surprised to hear XP-irradiation could do that!
|
| Yes, it appears it does that.... and more ! (not LOL) . But for now,
| let me be specific (as I was less than exact) in what I'm referring
| to.For example, I have files created in - and initially displayed in
| - W98se as:
| Blabla.txt
| Whatever pic.jpg
| File1009.jpg
What is the setting for "Allow all uppercase names" when they show up
like that? That's exactly what they would look like in Explorer, if the
box is unchecked.
| Then, after some back and forth between XP-radiation's-ville and W98se
| fallout shelter, I will then see in W98se (in Explorer/ some folder/
| whatever):
| BLABLA.TXT
| WHATEVER PIC.JPG
| FILE1009.JPG
Hmm. It could only show up this way in Explorer, if they really were
spelt like that AND the "Allow all..." option is checked.
|> | At any rate, the "solution" offered - eg - to disallow uppercase
|> | 'folder names' is unsatifactory (for me) as I do wish some folder
|> | names - but not necessarily *files* - to be in uppercase.
|>
|> That option in Win98 to "Allow all uppercase names", if checked,
|> actually allows both upper & lower case letters to show up-- whatever
|> the name really is! If the option is unchecked-- only the DISPLAY of
|> the name in Explorer is affected (not its actual spelling). Then,
|> the first letter shows up capitalized, & the rest lower-case.
|>
|> SO... it's up to you to spell them right in the first place-- & to
|> keep them away from XP!
|
| I try the former, and as for the latter: If W98se were still attended
| to with the reverence and care it deserves (from MS and software
| vendors and the like), I'd never venture into that Three-mile Island
| XP region for even one second. But alas.......
If you absolutely must use XP, best check for some weird setting in it
that could be respelling your file names. Does it have a "Folder
Options, View tab"? What are the options in there, then? Can it be XP
has one that really does respell a file name, instead of just changing
the way it displays in Explorer? And remember to put on your tinfoil hat
when sitting at an XP-machine! All of here do!
|> | Maybe this might not happen if one "hid" each respective OS from
|> | the other ?
|>
|> If XP-irradiation is really doing it, then, YEA-- NEVER allow XP to
|> see that partition!
|
| Then I must make everything that I might be able to access in W98se
| *invisible* to XP ? (I'm always trying to avoid any *System* related
| things already). Do you mean that even looking at 98se data from XP
| can be bad ? (I'm not talking about running 98se programs within XP).
I haven't sat at an XP-machine long enough to know or for my earlobes to
turn purple & fall onto my toes! Are you sure you just look at them in
XP? Does it happen every time?
Another possible way file names could become all upper-case is to copy
them in True DOS. Do you ever Reboot in MS-DOS Mode & do things to the
files there?
|> | Maybe it's a vexing -never to go away problem -, only
|> | resolved by constant application of a bulk renaming utility. lol
|> | :-/
|>
|> Yea. If you want the original Windows folders & files to actually be
|> spelled differently, you must do it yourself or find something like
|> that.
|
| Which is what I've had to do on more than one occasion. :-/
That sounds like a big pain!
Roxana
in 98se and try to avoid use of XP as much as possible).
<inline>
"PCR" wrote in message news:ORK1bMSE...@TK2MSFTNGP05.phx.gbl...
> Roxana wrote:
> | "PCR" wrote:
> |> Roxana wrote:
> |> | <snipp>....what are all lowercase in W98se,
> |> | somehow later get to be entirely uppercase - including the file
> |> | extension - when examined in W98se at some later time....
> |> | doubtless, after I've opened the folder or files in XPsp2.
> |>
> |> I'm not surprised to hear XP-irradiation could do that!
> |
> | let me be specific (as I was less than exact) in what I'm referring
> | - W98se as:
> | Blabla.txt
> | Whatever pic.jpg
> | File1009.jpg
>
> What is the setting for "Allow all uppercase names" when they show up
> like that? That's exactly what they would look like in Explorer, if the
> box is unchecked.
W98se: Files and Folders: Allow all uppercase names. *checked*
>
> | Then, after some back and forth between XP-radiation's-ville and W98se
> | fallout shelter, I will then see in W98se (in Explorer/ some folder/
> | whatever):
> | BLABLA.TXT
> | WHATEVER PIC.JPG
> | FILE1009.JPG
>
> Hmm. It could only show up this way in Explorer, if they really were
> spelt like that AND the "Allow all..." option is checked.
Which it is (in w98se). Again, it is *checked* (allowed)
>
> |> | At any rate, the "solution" offered - eg - to disallow uppercase
> |> | 'folder names' is unsatifactory (for me) as I do wish some folder
> |> | names - but not necessarily *files* - to be in uppercase.
> |>
> |> That option in Win98 to "Allow all uppercase names", if checked,
> |> actually allows both upper & lower case letters to show up-- whatever
> |> the name really is! If the option is unchecked-- only the DISPLAY of
> |> the name in Explorer is affected (not its actual spelling). Then,
> |> the first letter shows up capitalized, & the rest lower-case.
> |>
> |> SO... it's up to you to spell them right in the first place-- & to
> |> keep them away from XP!
> |
> | I try the former, and as for the latter: If W98se were still attended
> | to with the reverence and care it deserves (from MS and software
> | vendors and the like), I'd never venture into that Three-mile Island
> | XP region for even one second. But alas.......
>
> If you absolutely must use XP, best check for some weird setting in it
> that could be respelling your file names. Does it have a "Folder
> Options, View tab"?
It has some sort of something like that (accessed via a different menu
option than in 98se)
What are the options in there, then?
I cannot tell right now... I'm in w98se. I'll see later, OK ?
> Can it be XP
> has one that really does respell a file name, instead of just changing
> the way it displays in Explorer?
Hard to know. I seldom use it (I swear). hehe
And remember to put on your tinfoil hat
> when sitting at an XP-machine! All of here do!
You bet !
>
> |> | Maybe this might not happen if one "hid" each respective OS from
> |> | the other ?
> |>
> |> If XP-irradiation is really doing it, then, YEA-- NEVER allow XP to
> |> see that partition!
> |
> | Then I must make everything that I might be able to access in W98se
> | *invisible* to XP ? (I'm always trying to avoid any *System* related
> | things already). Do you mean that even looking at 98se data from XP
> | can be bad ? (I'm not talking about running 98se programs within XP).
>
> I haven't sat at an XP-machine long enough to know or for my earlobes to
> turn purple & fall onto my toes! Are you sure you just look at them in
> XP? Does it happen every time?
Maybe some are moved back and forth from time to time (Never any System type
stuff, mind you.). For instance, lets say I'm doing some photo editing or
some music / video editing. It sometimes seems better for me to copy or move
a given file from 98se over to XP for that purpose.
>
> Another possible way file names could become all upper-case is to copy
> them in True DOS. Do you ever Reboot in MS-DOS Mode & do things to the
> files there?
I've re-booted in MS-DOS on occasion, but have ultra rarely done any file
type stuff in that mode. Usually, I'd only boot into MS-DOS to do something
like a Deltree of TIF's.
>
> |> | Maybe it's a vexing -never to go away problem -, only
> |> | resolved by constant application of a bulk renaming utility. lol
> |> | :-/
> |>
> |> Yea. If you want the original Windows folders & files to actually be
> |> spelled differently, you must do it yourself or find something like
> |> that.
> |
> | Which is what I've had to do on more than one occasion. :-/
>
> That sounds like a big pain!
It's a smallish PITA. There are worse problems with PC's than that, of
course. It's probably the fact that one can use a bulk renaming utility in
... well, bulk, which makes it less annoying than it sounds. <g> But still,
it is annoying, and one must do something about it/them, or else live with
them as they become uppercase..
>
> |> |
> |> | "a" wrote in message
> |> | news:2em9h35hjknpueoeb...@4ax.com...
<snipped>
Roxana
"PCR" wrote in message news:ORK1bMSE...@TK2MSFTNGP05.phx.gbl...
> Roxana wrote:
<snipped>
> If you absolutely must use XP, best check for some weird setting in it
> that could be respelling your file names. Does it have a "Folder
> Options, View tab"?
In XP: Tools menu > folder options > view tab
> What are the options in there, then?
I see no option such as 98se has for names. There appears to be no "Allow
all uppercase names", or anything which I can perceive as applying to such a
similar option/ability.
> Can it be XP
> has one that really does respell a file name, instead of just changing
> the way it displays in Explorer?
<snipped>
I cannot rightly say, as my overall familiarity with XP pro is less than
nominal.
Does XP actually manage filename protocol differently than 9x; who knows ?
Is this issue solely limited to the way W98se *displays* these file names
which only *appear* to be uppercase when in 98se (after something,
somewhere, somehow has changed them so 98se sees them as such) ?
Whatever the case/cause may be (not filename "case"), 98se still *defacto*
displays some filenames which have mysteriously become changed to a FULLY
UPPERCASE name, and that's bad enough. These changed filenames can also be
manually re-named back to Lowercase in W98se. So, ultimately, the
"appearance" of the filename is changed - somehow, somewhere.
I know this much: Regardless of whatever OS I use - whether 98se or XP - I
never name files in FULL UPPERCASE, excepting for the first letter of a file
(or the first letter of each individual word of a given multiword file).
I may occasionally have reason to name a folder in FULL UPPERCASE in either
OS, but that's my limit of uppercase naming convention.
It's baffling, as well as being confusing to properly describe in words.
As I'd earlier hinted at, there are other areas where XP pro and 98se
'collide in strange fashion'. The Recycle Bin(s) are one area which readily
come to mind, but I just don't want to "go there' right now.
I should have added - though I'm not sure if this makes any difference -
that XP is on a second hard drive.
thanatoid
news:2em9h35hjknpueoeb...@4ax.com:
> hallo
<SNIP>
> in Explorer are always shown in uppercase
> if their name is up to 8 char long
> note:
> if the name is longer, eg: 12 char , it is shown in
> lower case
> note
> the files on the w98 same harddisk are always shown correctly
>
>
> How can I get the original lowercase filename
> from onther harddisk (or pen drive)
> correctly displayed in W98?
Seeing as the thread has not provided a simple answer, here's
one.
(For those who tend to read my blather, this will be
repetitious.)
IMO Windows Explorer is a torture device designed to let you do
the least possible with the most amount of hassle possible.
My suggestion is to NEVER use Windows Explorer again, except to
set file associations and stuff like that (e.g. options, which
CAN be accessed other ways or with specialized programs but
that's more than you want to get into).
Get a REAL file manager from www.ghisler.com
It will work forever in demo mode but I paid for it because I
could not live without it. Support independent authors who write
software that is your friend instead of your enemy.
I am PRETTY SURE your problem will disappear. Names appear like
you type them, and you have about 500 other features WE can only
dream of.
--
Waiting for the day when it is illegal to use anything but Vista
on any computer in the world.
Roxana
"thanatoid" wrote in message news:Xns99CCEED10...@66.250.146.158...
> a <a...@libero.it> wrote in
> news:2em9h35hjknpueoeb...@4ax.com:
>
> > hallo
>
> <SNIP>
>
> > in Explorer are always shown in uppercase
> > if their name is up to 8 char long
> > note:
> > if the name is longer, eg: 12 char , it is shown in
> > lower case
> > note
> > the files on the w98 same harddisk are always shown correctly
> >
> >
> > How can I get the original lowercase filename
> > from onther harddisk (or pen drive)
> > correctly displayed in W98?
>
>
> Get a REAL file manager from www.ghisler.com
> It will work forever in demo mode but I paid for it because I
> could not live without it. Support independent authors who write
> software that is your friend instead of your enemy.
>
> I am PRETTY SURE your problem will disappear. Names appear like
> you type them, and you have about 500 other features WE can only
> dream of.
>
> --
> Waiting for the day when it is illegal to use anything but Vista
> on any computer in the world.
First, before attending to actual reply. Your closing "tag", is that a fear,
or a wish ? :-D
Now:
I had that program - Total Commander - long ago (before dual boot with XP),
but had reason to un-install it, so therefore I cannot make any evaluation
as to whether that would "fix" the problem that has been described.
However, at the present, I have looked at this uppercase naming problem via
XYplorer, xplorer2, EFCommander, and other similar 3rd-party Windows
Explorer replacements and they all (eventually) manifest the same problem as
described.
Retuning once again to your suggestion: Am I mistaken in doubting that Total
Commander would be any more successful at curing this issue than any of the
other aforementioned file managers ?
I think there must be something that occurs when having two operating
systems (on separate drives ?) and possibly because they are not hidden from
each other (?) that's at the root of this. Obviously, I don't know the exact
reason or the answer.
BD
"Roxana" <somewher...@3rdStone.net> wrote in message
news:esL2FQUE...@TK2MSFTNGP02.phx.gbl...
code.
BD©
Franc Zabkar
finger to keyboard and composed:
>a wrote:
AFAICS, your explanation is valid if the original file name is all
caps, but the OP has stated that he/she saves her work using only
lowercase file names.
Franc Zabkar
<somewher...@3rdStone.net> put finger to keyboard and composed:
>I've seen similar activity from my near identical setup such as yours is.
>It's very annoying, as what are all lowercase in W98se, somehow later get to
>be entirely uppercase - including the file extension - when examined in
>W98se at some later time.... doubtless, after I've opened the folder or
>files in XPsp2.
The DOS 8.3 file name would be all caps and the long file name would
be mixed case. Maybe this is where multiple operating systems are
becoming confused ??? Does this phenomenon still occur for file names
that are longer than 8 characters? Is it possible that XP saves a
short file name in traditional DOS 8.3 uppercase format without
including a mixed case directory entry for its long equivalent?
a
>As I'd earlier hinted at, there are other areas where XP pro and 98se
>'collide in strange fashion'. The Recycle Bin(s) are one area which readily
>come to mind
I confirm.
a
>
>You SHOULD put the check into that box! Then, Explorer will show the
>actual name, unchanged-- capitals & lower case, whatever is really
>there!
no, no, my situation is different
That checkbox changes hallo.txt in HALLO.TXT
and I don't need it
My situation is about only the first capitalized letter:
I logged in XP, I created on XP drive the hallo.txt file
I logged in W98 , in Explorer, it is shown as Hallo.txt
I want it shown as hallo.txt (that is its original name)
Note:
Logged again in XP , in Explorer , it is regularly
shown as hallo.txt
here@hotmail.com MEB
"a" <a...@libero.it> wrote in message
news:3nleh3djm606off75...@4ax.com...
Beyond the issues related to XP and 9X in a networked or dual boot
situation:
Perhaps it would be viable to have you explain:
1. what programs you are using to design your pages;
2. upload your pages;
3. what type server your web page is hosted on [sounds like Apache or a
Linux].
4. whether you have access to, or can modify the .htaccess file and other
areas of the server.
In addition; from those knowledgeable:
a short discussion of issues related to MSDOS file names retained/handled in
XP verses 9X file/disk systems.
Though there has been a limited discussion, more exacting information would
definitely be conducive to resolving the issue.
--
MEB
http://peoplescounsel.orgfree.com
________
thanatoid
news:OrXbQMVE...@TK2MSFTNGP03.phx.gbl:
<SNIP>
> A solution to this could be scripted very quickly with
> about 10 lines of code.
God forbid a self-respecting geek would actually PROVIDE that
code for a user who has no clue about programming. It's just
about "I know and you don't", isn't it?
thanatoid
news:esL2FQUE...@TK2MSFTNGP02.phx.gbl:
It's called a "signature"
Neither. I am just waiting and observing a pleasant future
unfold daily. I use 95B and 98SE Lite.
> Now:
> I had that program - Total Commander - long ago (before
> dual boot with XP), but had reason to un-install it
Didn't like the total control over your computer? Just like to
suffer? Insanity run in your family?
> , so
> therefore I cannot make any evaluation as to whether that
> would "fix" the problem that has been described.
It's a 1MB (or something) DL.
< However,
> at the present, I have looked at this uppercase naming
> problem via XYplorer, xplorer2, EFCommander, and other
> similar 3rd-party Windows Explorer replacements and they
> all (eventually) manifest the same problem as described.
That's because they are all modified Explorers, just like there
are 30 "browsers" which are just front ends with a few extra
features and eye candy (what's important *is* important) for
that OTHER torture device and spyware machine, IE/OE.
> Retuning once again to your suggestion: Am I mistaken in
> doubting that Total Commander would be any more successful
> at curing this issue than any of the other aforementioned
> file managers ?
Since I see no reason on earth why ANYONE except an expert
technician - who probably would not have started this thread -
would have two OS's installed on a computer (therefore, you may
correctly deduce that I have not done it) I can't answer that
question. You are going to have to do something yourself. I gave
you a good suggestion. Do what you want.
> I think there must be something that occurs when having two
> operating systems (on separate drives ?) and possibly
> because they are not hidden from each other (?) that's at
> the root of this. Obviously, I don't know the exact reason
> or the answer.
Who knows, who cares? If you want to avoid stuff like this, use
a Mac or Linux. They have their own problems, of course. I
learned computers on Windows 3.1 etc. so that's why I am still
using Windows but I would not install Xtra Problems or Disasta
if you held a gun to my head. I have *NO* MS "software" on
either system except the OS's and those are VERY heavily tweaked
with software by people who know how to program.
a
my hoster doesn't allow me to upload
files with their first letter capitalized and their names longer then 8.3
I can't change that in any way.
PCR
Yea. It looks to me this is an XP problem. It doesn't handle file names
precisely the same as Win98 does, looks like. It isn't fully respecting
the advancement Windows instituted to provide the LFNs (Long File Names)
that Real DOS lacked! XP must be doing it a different way! (Now, I dimly
recall a distant thread that discussed this here once before-- but I
can't recall the details or whether there was a solution!)
I see elsewhere you said...
Franc Zabkar wrote:
| The DOS 8.3 file name would be all caps and the long file name would
| be mixed case. Maybe this is where multiple operating systems are
| becoming confused ??? Does this phenomenon still occur for file names
| that are longer than 8 characters? Is it possible that XP saves a
| short file name in traditional DOS 8.3 uppercase format without
| including a mixed case directory entry for its long equivalent?
Well, Roxana did post these possibilities for file names that are
affected...
Blabla.txt
Whatever pic.jpg
File1009.jpg
All of them will get switched to all upper-case, she said! So, this
phenonemon appears to affect both long & short file names. But when?
Does it happen even if the file is just opened to be read in XP? Or will
it only happen if the file is rewritten or renamed? I believe a (OP)
said the file name still will look good in XP, even after it has begun
to show up bad in Win98.
Hmmm... he may also be saying it only affects SFNs of files created on
the XP machine. I'll have to ask more questions of both of them. If this
is so, the problem may be that XP does not create a LFN for files whose
name would need it ONLY because it contains lower-case letters. A Real
DOS file name only can contain upper-case letters.
I'm trying real hard to collate both what Roxana & a have said & make
sense of it. What a puzzler!
BD
"thanatoid" <wai...@the.exit.invalid> wrote in message
news:Xns99CD810CE...@66.250.146.158...
> "BD" <Jus...@nothome.net> wrote in
> news:OrXbQMVE...@TK2MSFTNGP03.phx.gbl:
>
> <SNIP>
>
>> A solution to this could be scripted very quickly with
>> about 10 lines of code.
>
> God forbid a self-respecting geek would actually PROVIDE that
> code for a user who has no clue about programming. It's just
> about "I know and you don't", isn't it?
it EXCEPT that it's not written in a language that most people would be able
to use as a script. That is it's not vbs or js.
The only way for me to make it usable is to compile it to an executable and
for that they will have to ask for it. Then and only then will I upload the
file and provide a link to it.
PCR
|>You SHOULD put the check into that box! Then, Explorer will show the
|>actual name, unchanged-- capitals & lower case, whatever is really
|>there!
|
|
| no, no, my situation is different
Yea, I agree with you now-- two things are involved.
| That checkbox changes hallo.txt in HALLO.TXT
| and I don't need it
This means Explorer in Win98 really sees ALL capital letters in the
name. OR... it could mean... Explorer PRESUMES they are all capitalized.
| My situation is about only the first capitalized letter:
No. All the letters are capitalized or presumed to be capitalized. When
that "Allow all..." is checked, Explorer will not pretty up the name
(for display) by capitalizing the first letter & making the others
lower-case.
| I logged in XP, I created on XP drive the hallo.txt file
|
| I logged in W98 , in Explorer, it is shown as Hallo.txt
And I see you say, when you go back to XP, it shows up as "hallo.txt"
again. Also, you said earlier, when you create a long file name on XP--
it shows up just right even in Win98. Also, when you create one in
Win98, it shows up just fine in XP-- whether it is a short file name or
a long one.
THEREFORE... I think it is both a Win98 problem & an XP problem. When
JUST a SFN (Short File Name) exists-- Win98 will display it as all
upper-case letters. It presumes it is all upper-case, because that is
all Real DOS can handle, & it believes the name must have been created
in DOS. BUT Windows XP is putting mixed-case letters in there-- & NOT
creating a LFN (Long File Name) for it! If it created the LFN, Win98
would have picked up the proper case of the letters from there. Too bad
WinXP won't create the LFN when the reason to do it is only the case of
the letters! That's what I think it is! (And I dimly recall Blanton may
have said as much long ago too!)
The solution is to rename the file in Win98. Then, the LFN also will be
created, & the name will show up right in both 98 & XP. HOWEVER-- you
must also CHECK the "Allow all uppercase names" in the File Options of
Win98!
| I want it shown as hallo.txt (that is its original name)
|
| Note:
| Logged again in XP , in Explorer , it is regularly
| shown as hallo.txt
--
here@hotmail.com MEB
"a" <a...@libero.it> wrote in message
news:7ndfh3dch5nfan601...@4ax.com...
That leaves [per your part] the need for info on your programs used. Some
programs follow the Windows file naming scheme, others allow or convert to
lower case via options/settings.
As for the need for 8.3 names:
Often the failure is using *-* instead of *_* within a file name or having
blank spaces in the name.
Something like *my web page.htm* or *my-web-page.htm* fails, whereas
*my_web_page.htm* passes. Then there's always the user who tries to use
non-standard characters in the name, not realizing that the server may use
or add these for specific functions.
Most non-Microsoft servers generally follow the standards setup for the
Internet.
OTOH, Microsoft servers follow basic Windows ideas [yeah, let's let users
have web pages named like they see in Explorer on their systems, and as LONG
as possible [255c or more perhaps]. I have seen some page addresses almost
two hundred characters long [on Microsoft servers].... I mean REALLY, gees,
have they RTFM and RTFD on Internet standards... of course not, they live
in Microsoft's world of dreams ...
here@hotmail.com MEB
--
MEB
http://peoplescounsel.orgfree.com
________
"BD" <Jus...@nothome.net> wrote in message
news:upBpm8dE...@TK2MSFTNGP05.phx.gbl...
BD
"MEB" <meb@not he...@hotmail.com> wrote in message
news:eS2zmkeE...@TK2MSFTNGP03.phx.gbl...
> Before this degrades into a um, whatever, how about *I* ask for it....
>
> --
> MEB
> http://peoplescounsel.orgfree.com
> ________
http://dundats.mvps.org/Beta/File_LowerCas.zip
here@hotmail.com MEB
"BD" <Jus...@nothome.net> wrote in message
news:us65aIf...@TK2MSFTNGP03.phx.gbl...
Thank you, that's much appreciated.
Interesting code, was it compiled on/for XP? I get a "linked to missing
export KERNEL32.DLL, GetProcessIoCounters" in WinSE.. noted the reference to
uxtheme [among others] in the file.
BD
>
>
> Thank you, that's much appreciated.
>
> Interesting code, was it compiled on/for XP? I get a "linked to missing
> export KERNEL32.DLL, GetProcessIoCounters" in WinSE.. noted the reference
> to
> uxtheme [among others] in the file.
>
> --
> MEB
> http://peoplescounsel.orgfree.com
> ________
a file dialog and error handling included. There is really only 2 lines
that are required for the name change.
It was compiled on XP. I'm going to lay down for a bit and when I get up
I'll recompile the code for ANSI and post a separate link. I forgot to
change my auto-compile settings so it compiled in unicode.
9x systems do not have Unicode support but it will work fine on XP and the
OP has both.
PCR
| Try to answer here as best as, and as much as, I can at this time
| (I'm still in 98se and try to avoid use of XP as much as possible).
OK. But it's OK for you to drop this, if it's a lot of trouble going
back/forth. It seems you are happy enough just to rename them in Win98--
which I think is the only cure, anyhow. More below.
| <inline>
| "PCR" wrote in message news:ORK1bMSE...@TK2MSFTNGP05.phx.gbl...
|> Roxana wrote:
...snip
|> | Yes, it appears it does that.... But for now,
|> | let me be specific (as I was less than exact) in what I'm referring
|> | to. For example, I have files created in - and initially displayed
|> | in - W98se as:
|> | Blabla.txt
|> | Whatever pic.jpg
|> | File1009.jpg
|>
|> What is the setting for "Allow all uppercase names" when they show up
|> like that? That's exactly what they would look like in Explorer, if
|> the box is unchecked.
|
| W98se: Files and Folders: Allow all uppercase names. *checked*
OK-- keep that checkmark in that box, at least for the rest of these
experiments!
If you created the files spelt with lower-case letters in Win98, you are
getting BOTH a SFN (short) & a LFN (long) created for them. I would
think -- because they have the LFN -- XP would let them be, then.
|> | Then, after some back and forth between XP-radiation's-ville and
|> | W98se fallout shelter, I will then see in W98se (in Explorer/ some
|> | folder/ whatever):
|> | BLABLA.TXT
|> | WHATEVER PIC.JPG
|> | FILE1009.JPG
|>
|> Hmm. It could only show up this way in Explorer, if they really were
|> spelt like that AND the "Allow all..." option is checked.
|
| Which it is (in w98se). Again, it is *checked* (allowed)
Yea, good-- keep that checkmark in there, or you will see just one
capital letter!
It goes against my theory (that I posted to a) that XP could cause the
long one (WHATEVER PIC.JPG) to show up as all capitals when viewed on
the Win98 machine-- or even the other two! But especially the long one!
So, maybe verify it...?...
(A) Boot the Win98 machine, & create two files, spelt just like this...
Filename.txt
LongFileName.txt
(B) Copy them both to the XP drive.
Do the originals & the copies still look good?
(C) Boot the XP-machine.
Do all the names still look good?
(D) Rename just the originals that are on the Win98 drive.
You may rename to exactly the same names.
(E) Just open & close both the files on the XP-partition.
(F) Boot the Win98 machine.
How do all of the names look now?
...snip
|> If you absolutely must use XP, best check for some weird setting in
|> it that could be respelling your file names. Does it have a "Folder
|> Options, View tab"?
|
| It has some sort of something like that (accessed via a different menu
| option than in 98se)
|
| What are the options in there, then?
|
| I cannot tell right now... I'm in w98se. I'll see later, OK ?
OK, I see you posted that elsewhere. There was nothing useful.
|> Can it be XP
|> has one that really does respell a file name, instead of just
|> changing the way it displays in Explorer?
|
| Hard to know. I seldom use it (I swear). hehe
Good. Save it for the day Win98 crumbles to dust!
| And remember to put on your tinfoil hat
|> when sitting at an XP-machine! All of here do!
.......................................................... ^ us
|
| You bet !
Very good!
...snip
|> I haven't sat at an XP-machine long enough to know or for my
|> earlobes to turn purple & fall onto my toes! Are you sure you just
|> look at them in XP? Does it happen every time?
|
| Maybe some are moved back and forth from time to time (Never any
| System type stuff, mind you.). For instance, lets say I'm doing some
| photo editing or some music / video editing. It sometimes seems
| better for me to copy or move a given file from 98se over to XP for
| that purpose.
Once you copy it to XP, XP has to create its file name. But why won't it
just copy what already is there?
|>
|> Another possible way file names could become all upper-case is to
|> copy them in True DOS. Do you ever Reboot in MS-DOS Mode & do things
|> to the files there?
|
| I've re-booted in MS-DOS on occasion, but have ultra rarely done any
| file type stuff in that mode. Usually, I'd only boot into MS-DOS to
| do something like a Deltree of TIF's.
OK. That's not it, then.
|>
|> |> | Maybe it's a vexing -never to go away problem -, only
|> |> | resolved by constant application of a bulk renaming utility. lol
|> |> | :-/
|> |>
|> |> Yea. If you want the original Windows folders & files to actually
|> |> be spelled differently, you must do it yourself or find something
|> |> like that.
|> |
|> | Which is what I've had to do on more than one occasion. :-/
|>
|> That sounds like a big pain!
|
| It's a smallish PITA. There are worse problems with PC's than that, of
| course. It's probably the fact that one can use a bulk renaming
| utility in ... well, bulk, which makes it less annoying than it
| sounds. <g> But still, it is annoying, and one must do something
| about it/them, or else live with them as they become uppercase..
It is good you are content with that. I doubt anyone will find another
solution! This is from your other post...
| Does XP actually manage filename protocol differently than 9x; who
| knows ?
Yep. I think that's it. But when? And will it do it to all names-- long
ones & short ones? Does it matter on which machine they are first
created?
| Is this issue solely limited to the way W98se *displays*
| these file names which only *appear* to be uppercase when in 98se
| (after something, somewhere, somehow has changed them so 98se sees
| them as such) ?
No. Because it shows up messed up when "Allow all..." is checked,
something actually has happened to the name itself-- I think!
Apparently, the actual case of the letters do not change, because XP
still sees them as lower-case. BUT something about the name has changed
that prevents Win98 from seeing the case of the letters.
| Whatever the case/cause may be (not filename "case"), 98se still
| *defacto* displays some filenames which have mysteriously become
| changed to a FULLY UPPERCASE name, and that's bad enough. These
| changed filenames can also be manually re-named back to Lowercase in
| W98se. So, ultimately, the "appearance" of the filename is changed -
| somehow, somewhere.
Renaming them in Win98 makes the case understandable to Win98 again.
| I know this much: Regardless of whatever OS I use - whether 98se or
| XP - I never name files in FULL UPPERCASE, excepting for the first
| letter of a file (or the first letter of each individual word of a
| given multiword file).
Yea. Me too.
| I may occasionally have reason to name a folder in FULL UPPERCASE in
| either OS, but that's my limit of uppercase naming convention.
|
| It's baffling, as well as being confusing to properly describe in
| words.
Uhuh.
| As I'd earlier hinted at, there are other areas where XP pro and 98se
| 'collide in strange fashion'. The Recycle Bin(s) are one area which
| readily come to mind, but I just don't want to "go there' right now.
I know about that one too, but no solution.
| I should have added - though I'm not sure if this makes any
| difference - that XP is on a second hard drive.
I see. But it probably makes no difference. When XP boots, both drives
belong to XP. When 98 boots, both drives belong to it.
BD
http://dundats.mvps.org/Beta/File_LowerCaseA.zip
BD
Roxana
"Franc Zabkar" <fza...@iinternode.on.net> wrote in message
news:v33eh3hp98sac6kv9...@4ax.com...
Generally, I seem to recollect W98se displaying these "altered to FULL
UPPERCASE" filenames as rather short ones, leaning towards the 8-character
end. FILE1046.JPG would be one example. SAFARI22.JPG is another instance.
I cannot mentally see or recollect any instances where a name was actually
longer, now that you've mentioned it.
As for your questions, I'm sorry, but I haven't any idea. *ggg*
Roxana
Roxana
"a" <a...@libero.it> wrote:
OK thanks. So that one isn't just a figment of my imagination. I'm somewhat
relieved. :-D
Roxana
Roxana
You're timbre is too abrasive for me to care to deal with your 'reply'.
Roxana
--------------------------EOP--------------------------
"thanatoid" <wai...@the.exit.invalid> wrote in message
news:Xns99CD82F0F...@66.250.146.158...
> "Roxana" wrote in
Roxana
operating system; use WinXP pro - dual-booted - on rare occasions).
Would one require your intended/prospective 9x ANSI version to rectify this,
or would running (?) the XP coded unicode version in WinXP suffice ?
Thank you very much.
Roxana
PA Bear
> Tim Slattery wrote:
>> a <a...@libero.it> wrote:
>>
>>> How can I get the original lowercase filename
>>> from onther harddisk (or pen drive)
>>> correctly displayed in W98?
>>
>> start by checking View|Folder Options, View tab in Windows Explorer.
>> See if any of the options listed there might help out.
>>
> IIRC in Folder Options there is a setting to allow/disallow folder names
> in upper case.
You can run (away to sea), but you can't hide from us, Dundat! Howzaguy,
anyway? (glee squealed on you)
--
~Robear
thanatoid
news:upBpm8dE...@TK2MSFTNGP05.phx.gbl:
>
> "thanatoid" <wai...@the.exit.invalid> wrote in message
> news:Xns99CD810CE...@66.250.146.158...
>> "BD" <Jus...@nothome.net> wrote in
>> news:OrXbQMVE...@TK2MSFTNGP03.phx.gbl:
>>
>> <SNIP>
>>
>>> A solution to this could be scripted very quickly with
>>> about 10 lines of code.
>>
>> God forbid a self-respecting geek would actually PROVIDE
>> that code for a user who has no clue about programming.
>> It's just about "I know and you don't", isn't it?
> I wrote that code in 13 lines after I read the thread and
> would have posted it EXCEPT that it's not written in a
> language that most people would be able to use as a script.
You already stated that we are ignorant, no need to repeat
yourself.
> That is it's not vbs or js. The only way for me to make it
> usable is to compile it to an executable and for that they
> will have to ask for it. Then and only then will I upload
> the file and provide a link to it.
Yes, lord of all things scripted.
Will it be obligatory or just optional to come over and kiss
your ass repeatedly on-camera before you post it?
(BTW I am not interested, I just like being annoying.)
thanatoid
news:uhdOy#fEIHA...@TK2MSFTNGP03.phx.gbl:
<NOT SNIPPED FOR THE REQUIRED EFFECT>
Heaven help us all.
BD
news:ux5PuPgE...@TK2MSFTNGP05.phx.gbl...
> operating system; use WinXP pro - dual-booted - on rare occasions).
> Would one require your intended/prospective 9x ANSI version to rectify
> this,
> or would running (?) the XP coded unicode version in WinXP suffice ?
>
> Thank you very much.
> Roxana
>
running in 98 Then you need the ANSI version (which should also work in XP).
I posted that link as well
Just run the exe file, browse to the folder containing the files that you
want changed, select the files, slect OK and the selected files will be
changed. I didn't bother making this app folder recursive. That requires a
few more lines of code and I don't think that for what the OP needed that it
was worth adding in. If you have files to chang in more than 1 folder then
just run the app again for each folder.
BD
thanatoid
news:eHycgMgE...@TK2MSFTNGP05.phx.gbl:
> <top post>
Wow, you even felt the need to proudly announce it! Impressive!
> You're timbre is too abrasive for me to care to deal with
> your 'reply'. Roxana
"Your", not "you're", dear. And I must admit it's the first time
my attitude was called a timbre. Learning some new words these
days, are we?
> --------------------------EOP--------------------------
Then what are the 112 lines below? <not SNIPPED so you can see
what i'm talking about>
BD
news:Oc7gIVgE...@TK2MSFTNGP05.phx.gbl...
Zaguys hangin in there. Good to see you're still around. One of these days
I have to get my old address books (several, remember?) pulled into the new
systems and then just do a mass mailing bringing everyone up to date. There
goes the old bandwidth. <g>
Not really hanging around the groups yet but I thought I'd dip in the big
toe anyway. I was just doing my "Bear in the bush" imitation but there are
some things a guy just can't resist. Actually I just checked and it looks
(from memory anyway) that you have a new addy. Standby for incoming but it
will probably be tomorrow. If you try to send me mail use the bindar
account. If it goes to geog it will probably end up being destroyed. I'm
just starting to build a white list for that account that will solve the
problem.
BD
BD
> (BTW I am not interested, I just like being annoying.)
> --
> Waiting for the day when it is illegal to use anything but Vista
> on any computer in the world.
You must be fairly new around here hemmeroid (or using a new handle) or you
would already know that you and a thousand yappy puppies like you couldn't
upset me.
Been around too long for that.
here@hotmail.com MEB
--
MEB
http://peoplescounsel.orgfree.com
________
"BD" <Jus...@nothome.net> wrote in message
news:%233PSRBg...@TK2MSFTNGP04.phx.gbl...
BD
version should have fixed it. Have you tried it on an XP box? I had no
trouble and I tested it at least a dozen times.
"MEB" <meb@not he...@hotmail.com> wrote in message
news:O6qWKzgE...@TK2MSFTNGP02.phx.gbl...
Roxana
long day tomorrow which starts very -OMG, it's late !!! - early. Thanks.
Roxana (making this PCR one as *unread*)
"PCR" <pcr...@netzero.net> wrote in message
news:uhdOy%23fEIH...@TK2MSFTNGP03.phx.gbl...
<snipped>
thanatoid
news:uU3#dmgEIH...@TK2MSFTNGP02.phx.gbl:
Hey, Blowing Donkeys, if you're going to try to insult me, which
is impossible because letters and words are just strings of
black lines and curves, at least spell it right.
HEMORRHOID.
You could also try to be a little more original. Even thanaroid
was better.
Regards
t. (the goat-fucking attention whore)
Franc Zabkar
keyboard and composed:
>
>>
>>You SHOULD put the check into that box! Then, Explorer will show the
>>actual name, unchanged-- capitals & lower case, whatever is really
>>there!
>
>
>no, no, my situation is different
>
>That checkbox changes hallo.txt in HALLO.TXT
>and I don't need it
This behaviour suggests to me that the original XP file name is
written to the XP hard disc as all caps, not lowercase.
>My situation is about only the first capitalized letter:
>
>I logged in XP, I created on XP drive the hallo.txt file
>
>I logged in W98 , in Explorer, it is shown as Hallo.txt
>
>I want it shown as hallo.txt (that is its original name)
If you try the floppy diskette test that I described elsewhere, then
you will see the file name exactly as it is written to disc. I'm
betting you will see an all caps directory entry with no LFN
equivalent.
>Note:
>Logged again in XP , in Explorer , it is regularly
>shown as hallo.txt
- Franc Zabkar
Franc Zabkar
The following commands were executed in a Win98SE DOS box. I formatted
a floppy diskette and created one file named testfile.txt. The debug
output shows the 8.3 file name and LFN equivalent for this file. If I
do the same thing in real DOS mode, then only an 8.3 entry is created.
I suggest that you use whichever application that you normally use on
your XP machine to write a file to a clean floppy diskette. Then use
Debug to view the directory entry as I have done. I'm betting that the
LFN section (At.e.s.t.f...xi.l.e...t.x...t..) will not be there.
======================================================================
C:\WIN98SE>format a: /u
Insert new diskette for drive A:
and press ENTER when ready...
Formatting 1.44M
Format complete.
Volume label (11 characters, ENTER for none)? TEST
1,457,664 bytes total disk space
9,216 bytes in bad sectors
1,448,448 bytes available on disk
512 bytes in each allocation unit.
2,829 allocation units available on disk.
Volume Serial Number is 2D1A-18F5
Format another (Y/N)?n
C:\WIN98SE>rem > a:\testfile.txt <--- this creates a 0-byte file
C:\WIN98SE>dir a:
Volume in drive A is TEST
Volume Serial Number is 2D1A-18F5
Directory of A:\
TESTFILE TXT 0 10-19-07 5:31p testfile.txt
1 file(s) 0 bytes
0 dir(s) 1,448,448 bytes free
C:\WIN98SE>debug
-L 100 0 13 1
-D 100
100 54 45 53 54 20 20 20 20-20 20 20 28 00 00 00 00 TEST (....
110 00 00 00 00 00 00 D7 8B-53 37 00 00 00 00 00 00 ........S7......
120 41 74 00 65 00 73 00 74-00 66 00 0F 00 78 69 00 At.e.s.t.f...xi.
130 6C 00 65 00 2E 00 74 00-78 00 00 00 74 00 00 00 l.e...t.x...t...
140 54 45 53 54 46 49 4C 45-54 58 54 20 00 C6 E2 8B TESTFILETXT ....
150 53 37 53 37 00 00 E3 8B-53 37 00 00 00 00 00 00 S7S7....S7......
160 00 00 00 00 00 00 00 00-00 00 00 00 00 00 00 00 ................
170 00 00 00 00 00 00 00 00-00 00 00 00 00 00 00 00 ................
-Q
======================================================================
Franc Zabkar
<fza...@iinternode.on.net> put finger to keyboard and composed:
>On Thu, 18 Oct 2007 15:02:52 +0200, a <a...@libero.it> put finger to
>keyboard and composed:
>
>>
>>>
>>>You SHOULD put the check into that box! Then, Explorer will show the
>>>actual name, unchanged-- capitals & lower case, whatever is really
>>>there!
>>
>>
>>no, no, my situation is different
>>
>>That checkbox changes hallo.txt in HALLO.TXT
>>and I don't need it
>
>This behaviour suggests to me that the original XP file name is
>written to the XP hard disc as all caps, not lowercase.
Another way to verify the actual case of the file names is to type the
following in a Windows DOS box:
dir d:\ /b /s /p
where d: is the drive letter of your HD or pen drive.
Buffalo
[snip]
> (BTW I am not interested, I just like being annoying.)
I would rather be annoyed, than-a-toid; smelly,decaying, and disgusting? :)
See any humor in that.
here@hotmail.com MEB
the 9X test bed for it.
BTW: When we've covered this, I have some questions related to GEODISK.
--
MEB
http://peoplescounsel.orgfree.com
________
"BD" <Jus...@nothome.net> wrote in message
news:uSR4YEhE...@TK2MSFTNGP06.phx.gbl...
BD
> No I didn't. I knew you would do so before posting it. I thought I would
> be
> the 9X test bed for it.
> BTW: When we've covered this, I have some questions related to GEODISK.
>
> --
> MEB
> http://peoplescounsel.orgfree.com
> ________
You can Email those GEODisk questions to me.
It looks like the current problem is compiler related nothing to do with my
code. I have a Beta version of it loaded so I'll back up a couple of
versions and see what happens. I'll let you know when.
BD
thanatoid
news:9aydne8r1LFiJIXa...@comcast.com:
I never said a thanatoid is a thing to love and admire, let
alone smell at close distance.
a - MORE TESTS
I did more tests.
As told I have several HD and several Operative System
Tried XP and XP (another) : no problem
Tried WMe and W98 : no problem
Tried W2000 and W98 : problem (the same as XP and W98)
So the problem is (XP and W2000) + W98
Continued test with XP (forgot W2000).
Logged in XP, I created "hallo.txt" in:
- Floppy
- Same HD where XP lies
- Same HD wher XP lies, but different partition
- HD where W98 lies
- HD wher W98 lies, but different partition
- Pen Drive
All the 6 cases had the problem.
The problem occurs if the filename is 8 or less longer
The problem does NOT occur if the filename is 9 or more longer.
Tried to read the "hallo,txt" and "halloverylongfortesting.txt"
file from DOS (the W98 DOS);
I tried
dir c:\ /b /s /p
and I had displayed on the black screen
"HALLO.TXT" and "halloverylongfortesting.txt"
I have XP sp2 witn no NTFS
I have W98SE with FAT 32
Logged on XP there is no problem (never).
Logged on W98 there is the problem (ever).
If I log in W98 and manually un-capitalize "Hallo.txt" in "hallo.txt"
the problem is always solved,
but want the two OSes work proprerly they own.
BD
news:foqhh3p9ck01o8h0b...@4ax.com...
Just out of curiosity. Is it the server that won't accept uppercase? That
is really strange if that's the case. What are you using to FTP your files
to the server?
BD
BD
> No I didn't. I knew you would do so before posting it. I thought I would
> be
> the 9X test bed for it.
> BTW: When we've covered this, I have some questions related to GEODISK.
>
> --
> MEB
> http://peoplescounsel.orgfree.com
> ________
The bug has been fixed in the next compiler release but it's not available
yet. Also I asked on the developer forum and we are starting to think that
98 may not support all lower case. Several people are playing with it right
now to find out.
http://dundats.mvps.org/Beta/File_LowerCaseA.zip
For safety make sure that you just run this against test files.
Example
Create a folder on your desktop named Test
Create a few files named Test.txt, Test2.txt, Test3.txt etc.
Run the app against that folder.
BD
here@hotmail.com MEB
"BD" <Jus...@nothome.net> wrote in message
news:uNczeSoE...@TK2MSFTNGP04.phx.gbl...
| "MEB" <meb@not he...@hotmail.com> wrote in message
| news:uMb9v%23lEIH...@TK2MSFTNGP05.phx.gbl...
| > No I didn't. I knew you would do so before posting it. I thought I would
| > be
| > the 9X test bed for it.
| > BTW: When we've covered this, I have some questions related to GEODISK.
| >
| > --
| > MEB
| > ________
| I recompiled using a different version of the compiler. Hope it's right
now.
| The bug has been fixed in the next compiler release but it's not available
| yet. Also I asked on the developer forum and we are starting to think that
| 98 may not support all lower case. Several people are playing with it
right
| now to find out.
| http://dundats.mvps.org/Beta/File_LowerCaseA.zip
Well, my web site, retained locally, has upper and lower case files [and
mixed], so 98 does support lower case.
Moreover, I have hundreds of lower or mixed case files elsewhere. For
instance, the files I have been dowloading from you have a capital, whereas
most of my files and directories are lower case.
IMO, Since the NT file structure in XP is not held the same as in
DOS/9X/Fat, and handled via the ntfs driver upon creation, the *hook* to
Fat32 apparently retains the [original] MSDOS naming structure. IIRC, Seems
we did several lengthy discussions in here related to comparing those
structures, and posted [by various parties] several dozen KBs and other
materials during those discussions.
Regretfully, that newer file version also creates the same error.
|
| For safety make sure that you just run this against test files.
| Example
| Create a folder on your desktop named Test
| Create a few files named Test.txt, Test2.txt, Test3.txt etc.
| Run the app against that folder.
|
| BD
|
|
I'll have to go back to the site for your email addy, though I think I
tried that before and received no answer.
BD
I'll watch for it and then send you a safer address. Otherwise I just
remove all incoming mail from that account.
"MEB" <meb@not he...@hotmail.com> wrote in message
news:OyFva4oE...@TK2MSFTNGP03.phx.gbl...
Franc Zabkar
finger to keyboard and composed:
>Logged in XP, I created "hallo.txt" in:
>- Floppy
>- Same HD where XP lies
>- Same HD wher XP lies, but different partition
>- HD where W98 lies
>- HD wher W98 lies, but different partition
>- Pen Drive
>
>All the 6 cases had the problem.
>
>The problem occurs if the filename is 8 or less longer
>The problem does NOT occur if the filename is 9 or more longer.
>
>
>Tried to read the "hallo,txt" and "halloverylongfortesting.txt"
>file from DOS (the W98 DOS);
>I tried
>dir c:\ /b /s /p
>and I had displayed on the black screen
>"HALLO.TXT" and "halloverylongfortesting.txt"
I believe your test proves that it is your XP application that is
creating uppercase 8.3 file names. It doesn't appear to be a case
translation issue on your Win98 box. You can save us all a lot of time
and verify this beyond doubt by using Debug to look at the directory
structure on your floppy diskette.
To force XP to display the file name in its original case, follow this
procedure:
Force Explorer to Display Correct Filename Capitalization:
http://www.annoyances.org/exec/show/article02-101
a
My hosting company is Libero-Infostrada
The hosting service is free
The rules I accepted say no uppercase are allowed.
I ftp with 'CuteFTP'
If I ftp Hallo.htm the file is uploaded, but if i call it from the
browser, the browser say File Not Found
PCR
| On Fri, 19 Oct 2007 19:39:55 +0200, a - MORE TESTS <a...@libero.it> put
| finger to keyboard and composed:
|
|>Logged in XP, I created "hallo.txt" in:
|>- Floppy
|>- Same HD where XP lies
|>- Same HD wher XP lies, but different partition
|>- HD where W98 lies
|>- HD wher W98 lies, but different partition
|>- Pen Drive
|>
|>All the 6 cases had the problem.
|>
|>The problem occurs if the filename is 8 or less longer
|>The problem does NOT occur if the filename is 9 or more longer.
|>
|>
|>Tried to read the "hallo,txt" and "halloverylongfortesting.txt"
|>file from DOS (the W98 DOS);
|>I tried
|>dir c:\ /b /s /p
|>and I had displayed on the black screen
|>"HALLO.TXT" and "halloverylongfortesting.txt"
|
| I believe your test proves that it is your XP application that is
| creating uppercase 8.3 file names.
I've ruled that out as a possibility, because I believe he said the name
will continue to be lower-case when viewed in XP-- even after it has
begun to be capitalized in Win98...
news:3nleh3djm606off75...@4ax.com
| Note:
| Logged again in XP , in Explorer , it is regularly
| shown as hallo.txt
I'm thinking... Explorer in Win98 won't show true capitalization of a
file name, if all it has is a SFN (Short File Name). It presumes the SFN
is all capitals, because a Real DOS name always would be. XP is putting
the right case in there-- but not creating a LFN for it! I guess it just
doesn't consider a lower-case letter to be reason enough for it! (But
Win98 does consider it reason enough.)
| It doesn't appear to be a case
| translation issue on your Win98 box. You can save us all a lot of time
| and verify this beyond doubt by using Debug to look at the directory
| structure on your floppy diskette.
I think he WILL find the case to be correct in the SFN field-- & the LFN
field will be empty!
| To force XP to display the file name in its original case, follow this
| procedure:
|
| Force Explorer to Display Correct Filename Capitalization:
| http://www.annoyances.org/exec/show/article02-101
It is important to do as that article says! But I think it won't get
Explorer to show the true capitalization of a name-- UNLESS it is in the
LFN area.
If only Blanton could remember what he came up with the last time this
issue arose!
| - Franc Zabkar
| --
| Please remove one 'i' from my address when replying by email.
--
Thanks or Good Luck,
There may be humor in this post, and,
Naturally, you will not sue,
Should things get worse after this,
PCR
pcr...@netzero.net
thanatoid
news:ce9ih3pjm9ab7nunp...@4ax.com:
You get what you pay for. Sometimes. In this case, it appears
the saying applies.
a
i tried the
debug
-L 100 0 13 1
-D 100
-Q
with notepad
I created the short "hallo.txt"
and then the long "abccccccdef.txt"
I dumped with Dos from the XP box the two cases
ang got these screenshots:
http://www.zshare.net/image/43255032d60f26/
26 kb
note
I dumped with pure Dos on W98 the first case
and obtained the same result of the first previous one
note
I also created a short file "buon.zip" with WinZip
then dumped and got B. T7...... UON ZIP
I also created a short "ciao.htm" file with Firefox
then dumped and got T7.... IAO HTM
PCR
| "PCR" <pcr...@netzero.net> wrote in
| news:uhdOy#fEIHA...@TK2MSFTNGP03.phx.gbl:
...snip (I know it by heart)...
| <NOT SNIPPED FOR THE REQUIRED EFFECT>
|
| Heaven help us all.
Treble the thickness of your tinfoil hat in XP/Vista threads!
| --
| Waiting for the day when it is illegal to use anything but Vista
| on any computer in the world.
PCR
| I will attend to this one tomorrow evening PCR. I promise. I have a
| very long day tomorrow which starts very -OMG, it's late !!! -
| early. Thanks.
You are welcome. Mainly, I want to know for sure whether it happens to
LFNs as well as SFNs. (I think it does not.) A SFN is one in the 8.3
format, like FILENAME.TXT-- with no lower-case letters or spaces or
certain other special characters.
In Win98, I'm thinking, putting lower-case letters into it --
FileName.txt-- will trigger a LFN to be created. And I think that is not
triggered when the SFN is created in WinXP. XP will just put the
lower-case letters inside the SFN itself. Win98 won't see them there, I
think.
| Roxana (making this PCR one as *unread*)
| "PCR" <pcr...@netzero.net> wrote in message
| news:uhdOy%23fEIH...@TK2MSFTNGP03.phx.gbl...
| <snipped>
--
a
I repeat the problem
----------------
I boot on XP
I create "hallo.txt" with Notepad (or onther type of file
with Winzip, Firefox...) on the XP drive
then I boot on W98
and that file in Explorer
is shown as "Hallo.txt"
boot back in Xp it is ok (always)
boot again in W98 it is wrong (always)
I don't want the first letter capitalized
If , booted in W98, I manually rename the
first letter, uncapitalizing it, the problem is solved.
note:
if the name is longer then 8 (eg: halllotoeveryone.txt)
the problem doesn't occur
-------------------------
thanatoid
news:eg0c9DqE...@TK2MSFTNGP05.phx.gbl:
> thanatoid wrote:
>| "PCR" <pcr...@netzero.net> wrote in
>| news:uhdOy#fEIHA...@TK2MSFTNGP03.phx.gbl:
>
> ...snip (I know it by heart)...
>| <NOT SNIPPED FOR THE REQUIRED EFFECT>
>|
>| Heaven help us all.
>
> Treble the thickness of your tinfoil hat in XP/Vista
> threads!
BION, I don't wear one. A friendly witch doctor tells me the
mercury and lead residues in my brain should be protection
enough.
Still, WHAT are all these people blabbing on about XP and Vista
in this group? PLONK THE FUCKERS, I say.
LL DOS! LL 9x! LL Total Commander!! (FKA Windows Commander but
*guess* what happened.)
Hey PCR.... Maybe YOU can tell me... WHY would anyone want
to/need to run 98/XP on the *same* machine? Isn't life hard
enough? They could BUY a 98 machine for less than all the time
spent here torturing us with this 8.3 stuff, even charged at
minimum wage! And a KVM switch is $20!!!
I stand nonplussed (yet with mouth fully functional, always |-D)
before the ugly mysteries of life.
(Come to think of it, "UPPERCASE always from other units" is
almost as good as "all your base are belong to us".)
PA Bear
>> You can run (away to sea), but you can't hide from us, Dundat! Howzaguy,
>> anyway? (glee squealed on you)
>> --
> ...Standby for incoming but it
> will probably be tomorrow. If you try to send me mail use the bindar
> account. If it goes to geog it will probably end up being destroyed. I'm
> just starting to build a white list for that account that will solve the
> problem.
Same addy as in the past. My Gmail addy is intentionally munged in ReplyTo
when posting to NGs...but I'm sure you can figure out how to unmunge it, if
need be.
--
~Robear
Franc Zabkar
keyboard and composed:
The screenshots prove what I've been saying, ie that whenever the
names are in 8.3 format, they are written to the disc in uppercase.
The first screenshot shows two entries for HALLO.TXT. Apparently you
created a HALLO.TXT file and then deleted it. Then you created a
second HALLO.TXT. In each case only the 8.3 filename is/was written to
the disc, not its LFN. When you delete a file, its directory entry
isn't removed, only the leading character of the filename is changed
to 0xE5.
In the second screenshot you can see the LFN for abccccccdef.txt and
also its 8.3 name. In this instance the file has also been deleted.
>note
>I dumped with pure Dos on W98 the first case
>and obtained the same result of the first previous one
>
>note
>I also created a short file "buon.zip" with WinZip
>then dumped and got B. T7...... UON ZIP
>I also created a short "ciao.htm" file with Firefox
>then dumped and got T7.... IAO HTM
- Franc Zabkar
here@hotmail.com MEB
--
MEB
http://peoplescounsel.orgfree.com
________
"BD" <Jus...@nothome.net> wrote in message
news:eqr$yHpEIH...@TK2MSFTNGP04.phx.gbl...
BD
"PA Bear" <PABe...@gmail.com> wrote in message
news:uuArGOrE...@TK2MSFTNGP03.phx.gbl...
BD
when Unicode was first introduced into it which was about 8 months ago.
That's several releases now. I have a hunch that the new release of the
compiler will be pushed ahead because there were quite a few fixes this
time.news:e5EPswsE...@TK2MSFTNGP04.phx.gbl...
here@hotmail.com MEB
Perhaps a review of this Resource Kit document [and other] might help.
Read to understand XP's filing systems, down to the lower segments
http://www.microsoft.com/technet/prodtechnol/winxppro/reskit/c13621675.mspx
Or use this link [though you'll miss the necessary leadup related to 8.3
names, long file names, and blocked file entry aspects]. SEE:
File Naming in Windows XP Professional
File Names on FAT Volumes
Generating Short File Names
http://www.microsoft.com/technet/prodtechnol/winxppro/reskit/c13621675.mspx#EEIBG
Then over to [if Home Edition]:
http://www.microsoft.com/technet/prodtechnol/winxppro/reskit/z04d621675.mspx
--
MEB
http://peoplescounsel.orgfree.com
________
"Franc Zabkar" <fza...@iinternode.on.net> wrote in message
news:lhoih39cv8qmoh3hk...@4ax.com...
here@hotmail.com MEB
to XP [at least we're not discussing VISTA,, ooooowwww], ALL would be
necessarily included in the compiler updates for XP.
Let us know if you guys figure it out.
--
MEB
http://peoplescounsel.orgfree.com
________
"BD" <Jus...@nothome.net> wrote in message
news:OPeX$HtEIH...@TK2MSFTNGP06.phx.gbl...
Franc Zabkar
finger to keyboard and composed:
>Franc Zabkar wrote:
>| It doesn't appear to be a case
>| translation issue on your Win98 box. You can save us all a lot of time
>| and verify this beyond doubt by using Debug to look at the directory
>| structure on your floppy diskette.
>
>I think he WILL find the case to be correct in the SFN field-- & the LFN
>field will be empty!
I used Debug to change the SFN directory entry for a file named
TAILOR.MAK to tailor.mak. Below are the results (output edited for
clarity). Note that the original directory entries were all in
uppercase DOS 8.3 format with no LFNs.
!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!
WARNING: The "W(rite) command in DEBUG can do serious damage to your
file system if you get it wrong.
!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!
C:\WIN98SE>debug
-L 100 0 13 1
-D 100 10f
100 54 41 49 4C 4F 52 20 20-4D 41 4B 20 00 00 00 00 TAILOR MAK ....
-E 100 "tailor mak"
-D 100
100 74 61 69 6C 6F 72 20 20-6D 61 6B 20 00 00 00 00 tailor mak ....
110 00 00 00 00 00 00 97 A8-98 22 1B 00 91 00 00 00 ........."......
120 53 50 4F 55 53 45 20 20-45 58 45 20 00 00 00 00 SPOUSE EXE ....
130 00 00 F4 36 00 00 19 B0-98 22 49 00 21 1F 00 00 ...6....."I.!...
140 43 55 52 52 45 4E 43 59-46 52 4D 20 00 00 00 00 CURRENCYFRM ....
150 00 00 00 00 00 00 51 A3-98 22 06 00 5D 05 00 00 ......Q.."..]...
-W 100 0 13 1
-Q
C:\WIN98SE>dir a:\
Volume in drive A has no label
Directory of A:\
tailor mak 145 04-24-97 9:04p tailor.mak
SPOUSE EXE 7,969 04-24-97 10:00p SPOUSE.EXE
CURRENCY FRM 1,373 04-24-97 8:26p CURRENCY.FRM
...
CLA5-2 MAK 145 06-12-97 9:29p CLA5-2.MAK
42 file(s) 123,934 bytes
2 dir(s) 1,271,808 bytes free
a
other than renaming them (manually or by an utility)?
Franc Zabkar
put finger to keyboard and composed:
> Perhaps a review of this Resource Kit document [and other] might help.
>
> Read to understand XP's filing systems, down to the lower segments
>http://www.microsoft.com/technet/prodtechnol/winxppro/reskit/c13621675.mspx
I found the same document while researching for this thread but I
couldn't see anything that was helpful to the OP.
>Or use this link [though you'll miss the necessary leadup related to 8.3
>names, long file names, and blocked file entry aspects]. SEE:
>File Naming in Windows XP Professional
>File Names on FAT Volumes
>Generating Short File Names
>http://www.microsoft.com/technet/prodtechnol/winxppro/reskit/c13621675.mspx#EEIBG
>
> Then over to [if Home Edition]:
>
>http://www.microsoft.com/technet/prodtechnol/winxppro/reskit/z04d621675.mspx
- Franc Zabkar
Franc Zabkar
keyboard and composed:
>So there is way to have the filename correctly displayed in W98
>other than renaming them (manually or by an utility)?
The filename *is* correctly displayed in W98, it's just that XP
*saves* it as uppercase (but confuses you by *displaying* it as
lowercase) whenever it is in 8.3 format.
I suggest that you first add the "DontPrettyPath=1" setting to your
Win XP registry as described elsewhere. This will force Explorer to
display filenames with their actual capitalisation. Then here's one
possible way to tackle your problem from the XP end.
Let's say your files are .htm files. On the XP system try saving them
as .html files. This should force XP to create corresponding lowercase
LFNs for each of your 8.3 SFNs.
Now on your Win98SE system rename them like this ...
ren *.html *.htm
This should retain the LFNs and preserve their (lower)case.
If this workaround is unacceptable, let us know and I'll post a
question to the gurus at alt.msdos.batch.
Another possible solution involves 4DOS.com and this single command
line:
FOR %fn IN (*.txt) REN "%fn" %@REPLACE[ ,_,%@LOWER[" ",%fn]]
Let me know if you want to try this.
PCR
| in the case someone forgot the problem,
| I repeat the problem
|
| ----------------
|
| I boot on XP
| I create "hallo.txt" with Notepad (or onther type of file
| with Winzip, Firefox...) on the XP drive
My theory is... WinXP puts that name into the SFN (Short File Name)
field with the lower-case letters. It does not put anything into the LFN
field.
| then I boot on W98
| and that file in Explorer
| is shown as "Hallo.txt"
You are UNchecked for "Allow all uppercase names" at "Folder Options,
View tab". You must CHECK it-- or Win98 will always show just the 1st
letter to be capitalized! However, it begins to look to me that only
applies to SFNs. Once a LFN is created-- looks like it doesn't matter
whether that box is checked or not.
| boot back in Xp it is ok (always)
That proves the letters really are lower-case in the SFN field, I think.
| boot again in W98 it is wrong (always)
My theory is... Win98 will only get it right when there is a name in the
LFN field. It doesn't care what the case of the letters are in the SFN
field. It always shows the SFN to be capitalized!
| I don't want the first letter capitalized
|
| If , booted in W98, I manually rename the
| first letter, uncapitalizing it, the problem is solved.
When you create a name of any length in Win98 with lower-case letters--
a LFN will be created. Once that is done, the name will look good in
Win98 & in WinXP.
| note:
| if the name is longer then 8 (eg: halllotoeveryone.txt)
| the problem doesn't occur
WinXP is creating the LFN for that; so, all is well. Too bad it doesn't
do it when the only reason to do so is the case of the letters!
I think the only cure for SFNs with lower-case letters is to do as you
have been doing-- rename them in Win98. OR, just create them in Win98 in
the first place. Can't you do that?
| -------------------------
PCR
| On Fri, 19 Oct 2007 18:22:50 -0400, "PCR" <pcr...@netzero.net> put
| finger to keyboard and composed:
|
|>Franc Zabkar wrote:
|
|>| It doesn't appear to be a case
|>| translation issue on your Win98 box. You can save us all a lot of
|>| time and verify this beyond doubt by using Debug to look at the
|>| directory structure on your floppy diskette.
|>
|>I think he WILL find the case to be correct in the SFN field-- & the
|>LFN field will be empty!
|
| I used Debug to change the SFN directory entry for a file named
| TAILOR.MAK to tailor.mak. Below are the results (output edited for
| clarity). Note that the original directory entries were all in
| uppercase DOS 8.3 format with no LFNs.
|
| !!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!
| WARNING: The "W(rite) command in DEBUG can do serious damage to your
| file system if you get it wrong.
| !!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!
You are a brave one, Zabcar!
| C:\WIN98SE>debug
| -L 100 0 13 1
| -D 100 10f
| 100 54 41 49 4C 4F 52 20 20-4D 41 4B 20 00 00 00 00 TAILOR MAK ....
| -E 100 "tailor mak"
| -D 100
| 100 74 61 69 6C 6F 72 20 20-6D 61 6B 20 00 00 00 00 tailor mak ....
| 110 00 00 00 00 00 00 97 A8-98 22 1B 00 91 00 00 00 ........."......
| 120 53 50 4F 55 53 45 20 20-45 58 45 20 00 00 00 00 SPOUSE EXE ....
| 130 00 00 F4 36 00 00 19 B0-98 22 49 00 21 1F 00 00 ...6....."I.!...
| 140 43 55 52 52 45 4E 43 59-46 52 4D 20 00 00 00 00 CURRENCYFRM ....
| 150 00 00 00 00 00 00 51 A3-98 22 06 00 5D 05 00 00 ......Q.."..]...
| -W 100 0 13 1
| -Q
|
| C:\WIN98SE>dir a:\
|
| Volume in drive A has no label
| Directory of A:\
|
| tailor mak 145 04-24-97 9:04p tailor.mak
| SPOUSE EXE 7,969 04-24-97 10:00p SPOUSE.EXE
| CURRENCY FRM 1,373 04-24-97 8:26p CURRENCY.FRM
| ...
| CLA5-2 MAK 145 06-12-97 9:29p CLA5-2.MAK
| 42 file(s) 123,934 bytes
| 2 dir(s) 1,271,808 bytes free
It looks to me like you did get the SFN to show up as lower-case. BUT--
does it look like that in Explorer too? It would blow my theory, if it
does, presuming FAT12 (on a floppy, I think) would be the same FAT32.
My theory, you know, is that Explorer in Win98 doesn't care about the
case of letters in the SFN.
| - Franc Zabkar
| --
| Please remove one 'i' from my address when replying by email.
--
Franc Zabkar
finger to keyboard and composed:
>Franc Zabkar wrote:
>| C:\WIN98SE>dir a:\
>|
>| Volume in drive A has no label
>| Directory of A:\
>|
>| tailor mak 145 04-24-97 9:04p tailor.mak
>| SPOUSE EXE 7,969 04-24-97 10:00p SPOUSE.EXE
>| CURRENCY FRM 1,373 04-24-97 8:26p CURRENCY.FRM
>| ...
>| CLA5-2 MAK 145 06-12-97 9:29p CLA5-2.MAK
>| 42 file(s) 123,934 bytes
>| 2 dir(s) 1,271,808 bytes free
>
>It looks to me like you did get the SFN to show up as lower-case. BUT--
>does it look like that in Explorer too? It would blow my theory, if it
>does, presuming FAT12 (on a floppy, I think) would be the same FAT32.
>
>My theory, you know, is that Explorer in Win98 doesn't care about the
>case of letters in the SFN.
This is how it looks in W98 Explorer:
...
TAILOR.FRM
SPOUSE.MAK
tailor.mak
TRAFFIC.FRM
TRAFFIC.FRX
TRAFFIC.MAK
...
a
thanks for your concern,
but I think I'm going to give it up
all the solutions I'm going to face are too tricky
in my opinion
also because I have situation where in a same folder I have
a mixed case:
names with real first letter capitalized and names with
fake first letter capitalized,
so any batch renaming will fail
I was hoping just in a manual and defenitive setting
in the Registry or little more
here@hotmail.com MEB
Is an older version of the autocompiler available? One which was used
either during the *cross-over* time period {9X to XP} or before.
--
MEB
http://peoplescounsel.orgfree.com
________
"MEB" <meb@not he...@hotmail.com> wrote in message
news:uVxCLptE...@TK2MSFTNGP02.phx.gbl...
BD
> Continuing the thought process:
>
> Is an older version of the autocompiler available? One which was used
> either during the *cross-over* time period {9X to XP} or before.
>
> --
> MEB
> http://peoplescounsel.orgfree.com
> ________
re-write some of the code. I think if I just restore the last version that
did not have Unicode support it will work. A lot of code was broken when
Unicode was added. I'm expecting the patched version within a day or so.
BD
here@hotmail.com MEB
"BD" <Jus...@nothome.net> wrote in message
news:OuwDwhAF...@TK2MSFTNGP04.phx.gbl...
Okay, thanks for the update, seems *a* is getting a little antsy . . .
BD
>
>
> Okay, thanks for the update, seems *a* is getting a little antsy . . .
>
> --
> MEB
> http://peoplescounsel.orgfree.com
> ________
Antsy = The need for speed (NFS)
NFS = Things that are broken
PCR
That seems to break my theory. Are you sure there is STILL no LFN for
tailor.mac?
If XP is putting upper-case letters into SFNs & displaying them as
lower-case (which I think is your theory)-- why isn't it doing it to
LFNs as well? Didn't OP a say LFNs showed just up fine Win98 after they
were created in XP?
| - Franc Zabkar
| --
| Please remove one 'i' from my address when replying by email.
--
Franc Zabkar
I changed the case of a second filename using Debug and then enabled
the diskette's write-protect tab before quitting. This guarantees that
no LFN could have been written to the diskette. As with tailor.mak,
Explorer displays the second modified filename in lowercase.
>If XP is putting upper-case letters into SFNs & displaying them as
>lower-case (which I think is your theory)-- why isn't it doing it to
>LFNs as well? Didn't OP a say LFNs showed just up fine Win98 after they
>were created in XP?
I suspect that XP thinks that any 8.3 filename should follow the old
DOS 8.3 format, which is all caps. Unfortunately I don't have an XP
box to experiment with, otherwise I'd be testing this for myself.
PCR
I think that settles it. There is no reason to think FAT32 is unlike
FAT12 in its handling of SFNs. I can only believe it is untrue that
Explorer in Win98 would always show SFNs to be in upper-case no matter
what their case actually is & that for it to show lower-case letters
they would have to be in the LFN. My theory is blown!
|>If XP is putting upper-case letters into SFNs & displaying them as
|>lower-case (which I think is your theory)-- why isn't it doing it to
|>LFNs as well? Didn't OP a say LFNs showed just up fine Win98 after
|>they were created in XP?
|
| I suspect that XP thinks that any 8.3 filename should follow the old
| DOS 8.3 format, which is all caps.
That's what I thought Win98 must have been doing-- but it wasn't! Why
would XP do it? Also, why, then, would XP display them as lower-case? I
wonder what shows up in XP for a name like "FiLeNaMe.TxT"? Did anyone
say?
| Unfortunately I don't have an XP
| box to experiment with, otherwise I'd be testing this for myself.
Oh, you'd perish of irradiation on the 17th iteration! That is why it is
good a has quit & Roxana has taken a sabbatical!
| - Franc Zabkar
| --
| Please remove one 'i' from my address when replying by email.
--
here@hotmail.com MEB
--
MEB
http://peoplescounsel.orgfree.com
________
"BD" <Jus...@nothome.net> wrote in message
news:efGGHFC...@TK2MSFTNGP03.phx.gbl...
PCR
| 10-4
Hold DundatŽ's feet to the fire for that code, MEB! Even if he never
does come up with it-- at least it will be a cure for the saltwater
wrinkles between his toes!
--
Franc Zabkar
<fza...@iinternode.on.net> put finger to keyboard and composed:
>I suspect that XP thinks that any 8.3 filename should follow the old
>DOS 8.3 format, which is all caps. Unfortunately I don't have an XP
>box to experiment with, otherwise I'd be testing this for myself.
OK, I now have an XP box for testing.
I used Notepad to save a text file as ...
noquotes.txt
"withquot.txt"
longfilename.txt
Mix_CaSe.TxT
CAPITALS.TXT
XP Explorer displays the files exactly as saved, as does a Dir from a
CMD window.
However, on a W98 box the filenames are displayed as ...
NOQUOTES.TXT
WITHQUOT.TXT
longfilename.txt
Mix_CaSe.TxT
CAPITALS.TXT
Debug shows the following directory structure:
100 E5 4F 51 55 4F 54 45 53-54 58 54 20 18 40 8F 16 .OQUOTESTXT .@..
110 21 28 21 28 00 00 90 16-21 28 00 00 00 00 00 00 !(!(....!(......
120 4E 4F 51 55 4F 54 45 53-54 58 54 20 18 40 8F 16 NOQUOTESTXT .@..
130 21 28 21 28 00 00 90 16-21 28 02 00 04 00 00 00 !(!(....!(......
140 E5 49 54 48 51 55 4F 54-54 58 54 20 18 83 A0 16 .ITHQUOTTXT ....
150 21 28 21 28 00 00 A1 16-21 28 00 00 00 00 00 00 !(!(....!(......
160 57 49 54 48 51 55 4F 54-54 58 54 20 18 83 A0 16 WITHQUOTTXT ....
170 21 28 21 28 00 00 A2 16-21 28 03 00 04 00 00 00 !(!(....!(......
180 E5 74 00 78 00 74 00 00-00 FF FF 0F 00 D4 FF FF .t.x.t..........
190 FF FF FF FF FF FF FF FF-FF FF 00 00 FF FF FF FF ................
1A0 E5 6C 00 6F 00 6E 00 67-00 66 00 0F 00 D4 69 00 .l.o.n.g.f....i.
1B0 6C 00 65 00 6E 00 61 00-6D 00 00 00 65 00 2E 00 l.e.n.a.m...e...
1C0 E5 4F 4E 47 46 49 7E 31-54 58 54 20 00 BA AD 16 .ONGFI~1TXT ....
1D0 21 28 21 28 00 00 AE 16-21 28 00 00 00 00 00 00 !(!(....!(......
1E0 42 74 00 78 00 74 00 00-00 FF FF 0F 00 D4 FF FF Bt.x.t..........
1F0 FF FF FF FF FF FF FF FF-FF FF 00 00 FF FF FF FF ................
200 01 6C 00 6F 00 6E 00 67-00 66 00 0F 00 D4 69 00 .l.o.n.g.f....i.
210 6C 00 65 00 6E 00 61 00-6D 00 00 00 65 00 2E 00 l.e.n.a.m...e...
220 4C 4F 4E 47 46 49 7E 31-54 58 54 20 00 BA AD 16 LONGFI~1TXT ....
230 21 28 21 28 00 00 AF 16-21 28 04 00 04 00 00 00 !(!(....!(......
240 E5 4D 00 69 00 78 00 5F-00 43 00 0F 00 F5 61 00 .M.i.x._.C....a.
250 53 00 65 00 2E 00 54 00-78 00 00 00 54 00 00 00 S.e...T.x...T...
260 E5 49 58 5F 43 41 53 45-54 58 54 20 00 75 CE 16 .IX_CASETXT .u..
270 21 28 21 28 00 00 CF 16-21 28 00 00 00 00 00 00 !(!(....!(......
280 41 4D 00 69 00 78 00 5F-00 43 00 0F 00 F5 61 00 AM.i.x._.C....a.
290 53 00 65 00 2E 00 54 00-78 00 00 00 54 00 00 00 S.e...T.x...T...
2A0 4D 49 58 5F 43 41 53 45-54 58 54 20 00 75 CE 16 MIX_CASETXT .u..
2B0 21 28 21 28 00 00 D0 16-21 28 05 00 04 00 00 00 !(!(....!(......
...
300 E5 41 50 49 54 41 4C 53-54 58 54 20 00 20 2E 18 .APITALSTXT . ..
310 21 28 21 28 00 00 2F 18-21 28 00 00 00 00 00 00 !(!(../.!(......
320 43 41 50 49 54 41 4C 53-54 58 54 20 00 20 2E 18 CAPITALSTXT . ..
330 21 28 21 28 00 00 2F 18-21 28 08 00 04 00 00 00 !(!(../.!(......
This structure strikes me as peculiar because, although there are
several entries that suggest that files have been deleted, I have not
in fact deleted any.
I can see why W98 displays the filenames as it does, but I can't
understand how XP knows that CAPITALSTXT was originally saved as
uppercase and NOQUOTESTXT was saved as lowercase (I've rebooted the
machine between tests).
More testing is in order ...
Franc Zabkar
<fza...@iinternode.on.net> put finger to keyboard and composed:
>I can see why W98 displays the filenames as it does, but I can't
>understand how XP knows that CAPITALSTXT was originally saved as
>uppercase and NOQUOTESTXT was saved as lowercase (I've rebooted the
>machine between tests).
>
>More testing is in order ...
Here is the directory structure after I created a file named
UPPRCASE.TXT using Notepad:
100 E5 50 50 52 43 41 53 45-54 58 54 20 00 28 97 2A .PPRCASETXT .(.*
110 21 28 21 28 00 00 98 2A-21 28 00 00 00 00 00 00 !(!(...*!(......
120 55 50 50 52 43 41 53 45-54 58 54 20 00 28 97 2A UPPRCASETXT .(.*
130 21 28 21 28 00 00 98 2A-21 28 02 00 06 00 00 00 !(!(...*!(......
Here is the same structure after renaming UPPRCASE.TXT to lowrcase.txt
in Explorer:
100 E5 50 50 52 43 41 53 45-54 58 54 20 00 28 97 2A .PPRCASETXT .(.*
110 21 28 21 28 00 00 98 2A-21 28 00 00 00 00 00 00 !(!(...*!(......
120 4C 4F 57 52 43 41 53 45-54 58 54 20 18 28 97 2A LOWRCASETXT .(.*
130 21 28 21 28 00 00 98 2A-21 28 02 00 06 00 00 00 !(!(...*!(......
After renaming lowrcase.txt back to UPPRCASE.TXT, the first structure
was restored.
There is one byte (location 12C) that appears to determine whether a
filename is all uppercase (value = 0x00) or all lowercase (value =
0x18). To test this hypothesis I used Debug to change the value of
this byte from 00 to 0x18. XP then displayed the filename as
upprcase.txt, which I believe confirms my observation. So it seems
that this byte means something to XP but is ignored by Win9x and DOS.
In summary I believe that XP will write both an SFN and LFN if the
filename is not in 8.3 format, or if the filename is MiXeD CaSe 8.3.
Otherwise it will write an SFN with a special byte that indicates
whether the filename is ALL CAPS or all lowercase.
Franc Zabkar
<fza...@iinternode.on.net> put finger to keyboard and composed:
>There is one byte (location 12C) that appears to determine whether a
>filename is all uppercase (value = 0x00) or all lowercase (value =
>0x18). To test this hypothesis I used Debug to change the value of
>this byte from 00 to 0x18. XP then displayed the filename as
>upprcase.txt, which I believe confirms my observation. So it seems
>that this byte means something to XP but is ignored by Win9x and DOS.
>
>In summary I believe that XP will write both an SFN and LFN if the
>filename is not in 8.3 format, or if the filename is MiXeD CaSe 8.3.
>Otherwise it will write an SFN with a special byte that indicates
>whether the filename is ALL CAPS or all lowercase.
After some more thought it occurred to me that the difference between
0x18 and 0x00 is in two bits, and that 2 bits can code for 4 states.
Additional experimentation reveals that the "special" byte is coded as
follows:
0x00 --> FILENAME.EXT
0x18 --> filename.ext
0x10 --> FILENAME.ext
0x08 --> filename.EXT
If the OP is watching, then a workaround for his/her problem would be
to rename the files on the XP system as follows ...
ren *.htm *.Htm
ren *.txt *.Txt
ren *.gif *.Gif
... and then on the W98 system restore their original names ...
ren *.Htm *.htm
ren *.Txt *.txt
ren *.Gif *.gif
BTW, here is Microsoft's FAT32 File System Specification:
http://www.microsoft.com/whdc/system/platform/firmware/fatgen.mspx
The "special" byte is documented as follows:
"Reserved for use by Windows NT. Set value to 0 when a file is created
and never modify or look at it after that."
a
<fza...@iinternode.on.net> wrote:
>If the OP is watching, then a workaround for his/her problem would be
>to rename the files on the XP system as follows ...
>
> ren *.htm *.Htm
> ren *.txt *.Txt
> ren *.gif *.Gif
>
>... and then on the W98 system restore their original names ...
>
> ren *.Htm *.htm
> ren *.Txt *.txt
> ren *.Gif *.gif
i'm here (i'm a man)
but I don't understant why now we are facing extensions
also
I prefer to rename file only once (from W98)
(I don't want rename anything indeed...)
PCR
---- Original Message ----
From: "Franc Zabkar" <fza...@iinternode.on.net>
Newsgroups: microsoft.public.win98.gen_discussion
Sent: Tuesday, October 23, 2007 05:21 AM
Subject: Re: UPPERCASE always from other units
| On Mon, 22 Oct 2007 07:20:20 +1000, Franc Zabkar
| <fza...@iinternode.on.net> put finger to keyboard and composed:
|
|>I suspect that XP thinks that any 8.3 filename should follow the old
|>DOS 8.3 format, which is all caps. Unfortunately I don't have an XP
|>box to experiment with, otherwise I'd be testing this for myself.
|
| OK, I now have an XP box for testing.
|
| I used Notepad to save a text file as ...
|
| noquotes.txt
| "withquot.txt"
| longfilename.txt
| Mix_CaSe.TxT
| CAPITALS.TXT
|
| XP Explorer displays the files exactly as saved, as does a Dir from a
| CMD window.
|
| However, on a W98 box the filenames are displayed as ...
|
| NOQUOTES.TXT
| WITHQUOT.TXT
So, it is only 8.3 names of all lower-case that will show up badly in
Win98, after they were created in WinXP.
| longfilename.txt
| Mix_CaSe.TxT
| CAPITALS.TXT
|
| Debug shows the following directory structure:
|
| 100 E5 4F 51 55 4F 54 45 53-54 58 54 20 18 40 8F 16 .OQUOTESTXT .@..
| 110 21 28 21 28 00 00 90 16-21 28 00 00 00 00 00 00 !(!(....!(......
| 120 4E 4F 51 55 4F 54 45 53-54 58 54 20 18 40 8F 16 NOQUOTESTXT .@..
| 130 21 28 21 28 00 00 90 16-21 28 02 00 04 00 00 00 !(!(....!(......
| 140 E5 49 54 48 51 55 4F 54-54 58 54 20 18 83 A0 16 .ITHQUOTTXT ....
| 150 21 28 21 28 00 00 A1 16-21 28 00 00 00 00 00 00 !(!(....!(......
| 160 57 49 54 48 51 55 4F 54-54 58 54 20 18 83 A0 16 WITHQUOTTXT ....
| 170 21 28 21 28 00 00 A2 16-21 28 03 00 04 00 00 00 !(!(....!(......
| 180 E5 74 00 78 00 74 00 00-00 FF FF 0F 00 D4 FF FF .t.x.t..........
| 190 FF FF FF FF FF FF FF FF-FF FF 00 00 FF FF FF FF ................
| 1A0 E5 6C 00 6F 00 6E 00 67-00 66 00 0F 00 D4 69 00 .l.o.n.g.f....i.
| 1B0 6C 00 65 00 6E 00 61 00-6D 00 00 00 65 00 2E 00 l.e.n.a.m...e...
| 1C0 E5 4F 4E 47 46 49 7E 31-54 58 54 20 00 BA AD 16 .ONGFI~1TXT ....
| 1D0 21 28 21 28 00 00 AE 16-21 28 00 00 00 00 00 00 !(!(....!(......
| 1E0 42 74 00 78 00 74 00 00-00 FF FF 0F 00 D4 FF FF Bt.x.t..........
| 1F0 FF FF FF FF FF FF FF FF-FF FF 00 00 FF FF FF FF ................
| 200 01 6C 00 6F 00 6E 00 67-00 66 00 0F 00 D4 69 00 .l.o.n.g.f....i.
| 210 6C 00 65 00 6E 00 61 00-6D 00 00 00 65 00 2E 00 l.e.n.a.m...e...
| 220 4C 4F 4E 47 46 49 7E 31-54 58 54 20 00 BA AD 16 LONGFI~1TXT ....
| 230 21 28 21 28 00 00 AF 16-21 28 04 00 04 00 00 00 !(!(....!(......
This is what XP did for "Mix_CaSe.TxT"...?...
| 240 E5 4D 00 69 00 78 00 5F-00 43 00 0F 00 F5 61 00 .M.i.x._.C....a.
| 250 53 00 65 00 2E 00 54 00-78 00 00 00 54 00 00 00 S.e...T.x...T...
| 260 E5 49 58 5F 43 41 53 45-54 58 54 20 00 75 CE 16 .IX_CASETXT .u..
| 270 21 28 21 28 00 00 CF 16-21 28 00 00 00 00 00 00 !(!(....!(......
| 280 41 4D 00 69 00 78 00 5F-00 43 00 0F 00 F5 61 00 AM.i.x._.C....a.
| 290 53 00 65 00 2E 00 54 00-78 00 00 00 54 00 00 00 S.e...T.x...T...
| 2A0 4D 49 58 5F 43 41 53 45-54 58 54 20 00 75 CE 16 MIX_CASETXT .u..
| 2B0 21 28 21 28 00 00 D0 16-21 28 05 00 04 00 00 00 !(!(....!(......
| ...
How does Win98 display it right from that? I guess the 1st four lines
are the "deleted" file, & the next four are a LFN & a SFN (which I'd
have thought should be reversed in order, though-- the SFN 1st). looks
like Win98 is getting it from the LFN, which was part of my own original
theory-- that all would be well once a LFN was created. In your earlier
doings, it seemed Win98 (Explorer & DOS) was able to pick up lower-case
names from the SFN itself-- but, in that case, there was no LFN to
choose from.
| 300 E5 41 50 49 54 41 4C 53-54 58 54 20 00 20 2E 18 .APITALSTXT . ..
| 310 21 28 21 28 00 00 2F 18-21 28 00 00 00 00 00 00 !(!(../.!(......
| 320 43 41 50 49 54 41 4C 53-54 58 54 20 00 20 2E 18 CAPITALSTXT . ..
| 330 21 28 21 28 00 00 2F 18-21 28 08 00 04 00 00 00 !(!(../.!(......
|
| This structure strikes me as peculiar because, although there are
| several entries that suggest that files have been deleted, I have not
| in fact deleted any.
Very weird! But, I suppose no real harm is done.
| I can see why W98 displays the filenames as it does, but I can't
| understand how XP knows that CAPITALSTXT was originally saved as
| uppercase and NOQUOTESTXT was saved as lowercase (I've rebooted the
| machine between tests).
|
| More testing is in order ...
|
| - Franc Zabkar
| --
| Please remove one 'i' from my address when replying by email.
| On Tue, 23 Oct 2007 19:21:37 +1000, Franc Zabkar
| <fza...@iinternode.on.net> put finger to keyboard and composed:
|
|>I can see why W98 displays the filenames as it does, but I can't
|>understand how XP knows that CAPITALSTXT was originally saved as
|>uppercase and NOQUOTESTXT was saved as lowercase (I've rebooted the
|>machine between tests).
|>
|>More testing is in order ...
|
| Here is the directory structure after I created a file named
| UPPRCASE.TXT using Notepad:
|
| 100 E5 50 50 52 43 41 53 45-54 58 54 20 00 28 97 2A .PPRCASETXT .(.*
| 110 21 28 21 28 00 00 98 2A-21 28 00 00 00 00 00 00 !(!(...*!(......
| 120 55 50 50 52 43 41 53 45-54 58 54 20 00 28 97 2A UPPRCASETXT .(.*
| 130 21 28 21 28 00 00 98 2A-21 28 02 00 06 00 00 00 !(!(...*!(......
|
| Here is the same structure after renaming UPPRCASE.TXT to lowrcase.txt
| in Explorer:
|
| 100 E5 50 50 52 43 41 53 45-54 58 54 20 00 28 97 2A .PPRCASETXT .(.*
| 110 21 28 21 28 00 00 98 2A-21 28 00 00 00 00 00 00 !(!(...*!(......
| 120 4C 4F 57 52 43 41 53 45-54 58 54 20 18 28 97 2A LOWRCASETXT .(.*
| 130 21 28 21 28 00 00 98 2A-21 28 02 00 06 00 00 00 !(!(...*!(......
|
| After renaming lowrcase.txt back to UPPRCASE.TXT, the first structure
| was restored.
That is good that yet another deleted name doesn't result!
| There is one byte (location 12C) that appears to determine whether a
| filename is all uppercase (value = 0x00) or all lowercase (value =
| 0x18). To test this hypothesis I used Debug to change the value of
| this byte from 00 to 0x18. XP then displayed the filename as
| upprcase.txt, which I believe confirms my observation. So it seems
| that this byte means something to XP but is ignored by Win9x and DOS.
Yep! Very good! But it does put the correct case in all LFNs, (right?).
| In summary I believe that XP will write both an SFN and LFN if the
| filename is not in 8.3 format, or if the filename is MiXeD CaSe 8.3.
| Otherwise it will write an SFN with a special byte that indicates
| whether the filename is ALL CAPS or all lowercase.
Uhuh. Very good!
| - Franc Zabkar
| --
| Please remove one 'i' from my address when replying by email.
| On Tue, 23 Oct 2007 20:37:00 +1000, Franc Zabkar
| <fza...@iinternode.on.net> put finger to keyboard and composed:
|
|>There is one byte (location 12C) that appears to determine whether a
|>filename is all uppercase (value = 0x00) or all lowercase (value =
|>0x18). To test this hypothesis I used Debug to change the value of
|>this byte from 00 to 0x18. XP then displayed the filename as
|>upprcase.txt, which I believe confirms my observation. So it seems
|>that this byte means something to XP but is ignored by Win9x and DOS.
|>
|>In summary I believe that XP will write both an SFN and LFN if the
|>filename is not in 8.3 format, or if the filename is MiXeD CaSe 8.3.
|>Otherwise it will write an SFN with a special byte that indicates
|>whether the filename is ALL CAPS or all lowercase.
|
| After some more thought it occurred to me that the difference between
| 0x18 and 0x00 is in two bits, and that 2 bits can code for 4 states.
| Additional experimentation reveals that the "special" byte is coded as
| follows:
|
| 0x00 --> FILENAME.EXT
| 0x18 --> filename.ext
| 0x10 --> FILENAME.ext
| 0x08 --> filename.EXT
Yow! Why?? There was never any such thing even in DOS-- that the name
could be a different case than the extension!
| If the OP is watching, then a workaround for his/her problem would be
| to rename the files on the XP system as follows ...
|
| ren *.htm *.Htm
| ren *.txt *.Txt
| ren *.gif *.Gif
|
| ... and then on the W98 system restore their original names ...
|
| ren *.Htm *.htm
| ren *.Txt *.txt
| ren *.Gif *.gif
Is it necessary to rename them first in XP? And why are you renaming
just the extensions? I'd have though just renaming upper to lower-case
in 98 would create the LFN. And didn't a say all was well after doing
that?
| BTW, here is Microsoft's FAT32 File System Specification:
| http://www.microsoft.com/whdc/system/platform/firmware/fatgen.mspx
|
| The "special" byte is documented as follows:
|
| "Reserved for use by Windows NT. Set value to 0 when a file is created
| and never modify or look at it after that."
|
| - Franc Zabkar
| --
| Please remove one 'i' from my address when replying by email.
Thanks or Good Luck,
Franc Zabkar
keyboard and composed:
>On Wed, 24 Oct 2007 06:08:45 +1000, Franc Zabkar
Win98 sees all 8.3 short filenames as uppercase, even if they were
created with lowercase. To work around this limitation, you need to
force XP to add a long filename directory entry for each 8.3 file. The
only easy way I can see to do that (using built-in tools) is to create
a filename with mixed case at the XP end and then convert it to
lowercase at the W98 end.
Otherwise, there is the 4DOS method I alluded to elsewhere.
4DOS.com is a freeware equivalent for command.com with many additional
features.