Where do you put the autoexec lines for a dosbox?

"PCR" wrote in message ...
Bill Blanton wrote:

In DOS you can test this by doing
DIR /-o
DEL (some file in the middle)
COPY CON XXXXXXXXX.XXX (type a char, then F6)
Then do another DIR /-o

C:\dir windows\temp
...snip
NULLSO~1 DLL 59,392 03-18-09 9:57p NullsoftHelper.dll
JUNK TXT 110,592 03-17-07 9:23p junk.txt
CONTROL XML 12,818 07-07-09 6:06p control.xml
...snip

C:\dir windows\temp
...snip
NULLSO~1 DLL 59,392 03-18-09 9:57p NullsoftHelper.dll
XXXXXX~1 XXX 1 08-22-09 12:06a XXXXXXXXX.XXX
CONTROL XML 12,818 07-07-09 6:06p control.xml
...snip

You could also confirm that in a disk editor.

I'm happy enough as is.

I just noticed that you created a long name XXXXXXXXX.XXX.
Luckily junk.txt was an LFN too.. or there'd be some splainin
to do.

Bill Blanton wrote:
"PCR" wrote in message
...
Bill Blanton wrote:

In DOS you can test this by doing
DIR /-o
DEL (some file in the middle)
COPY CON XXXXXXXXX.XXX (type a char, then F6)
Then do another DIR /-o

C:\dir windows\temp
...snip
NULLSO~1 DLL 59,392 03-18-09 9:57p NullsoftHelper.dll
JUNK TXT 110,592 03-17-07 9:23p junk.txt
CONTROL XML 12,818 07-07-09 6:06p control.xml
...snip

C:\dir windows\temp
...snip
NULLSO~1 DLL 59,392 03-18-09 9:57p NullsoftHelper.dll
XXXXXX~1 XXX 1 08-22-09 12:06a XXXXXXXXX.XXX
CONTROL XML 12,818 07-07-09 6:06p control.xml
...snip

You could also confirm that in a disk editor.

I'm happy enough as is.

I just noticed that you created a long name XXXXXXXXX.XXX.
Luckily junk.txt was an LFN too.. or there'd be some splainin
to do.

That might get confusing to contemplate. Suppose a LFN file is deleted &
replaced a SFN file. If the SFN file is now deleted, I guess the slot
might be usable for a LFN.


--
Thanks or Good Luck,
There may be humor in this post, and,
Naturally, you will not sue,
Should things get worse after this,
PCR

Bill Blanton wrote:
"PCR" wrote in message
...
Bill Blanton wrote:

In DOS you can test this by doing
DIR /-o
DEL (some file in the middle)
COPY CON XXXXXXXXX.XXX (type a char, then F6)
Then do another DIR /-o

C:\dir windows\temp
...snip
NULLSO~1 DLL 59,392 03-18-09 9:57p NullsoftHelper.dll
JUNK TXT 110,592 03-17-07 9:23p junk.txt
CONTROL XML 12,818 07-07-09 6:06p control.xml
...snip

C:\dir windows\temp
...snip
NULLSO~1 DLL 59,392 03-18-09 9:57p NullsoftHelper.dll
XXXXXX~1 XXX 1 08-22-09 12:06a XXXXXXXXX.XXX
CONTROL XML 12,818 07-07-09 6:06p control.xml
...snip

You could also confirm that in a disk editor.

I'm happy enough as is.

I just noticed that you created a long name XXXXXXXXX.XXX.
Luckily junk.txt was an LFN too.. or there'd be some splainin
to do.

That might get confusing to contemplate. Suppose a LFN file is deleted &
replaced a SFN file. If the SFN file is now deleted, I guess the slot
might be usable for a LFN.


--
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" wrote in message ...
Bill Blanton wrote:
"PCR" wrote in message
...
Bill Blanton wrote:

In DOS you can test this by doing
DIR /-o
DEL (some file in the middle)
COPY CON XXXXXXXXX.XXX (type a char, then F6)
Then do another DIR /-o

C:\dir windows\temp
...snip
NULLSO~1 DLL 59,392 03-18-09 9:57p NullsoftHelper.dll
JUNK TXT 110,592 03-17-07 9:23p junk.txt
CONTROL XML 12,818 07-07-09 6:06p control.xml
...snip

C:\dir windows\temp
...snip
NULLSO~1 DLL 59,392 03-18-09 9:57p NullsoftHelper.dll
XXXXXX~1 XXX 1 08-22-09 12:06a XXXXXXXXX.XXX
CONTROL XML 12,818 07-07-09 6:06p control.xml
...snip

You could also confirm that in a disk editor.

I'm happy enough as is.

I just noticed that you created a long name XXXXXXXXX.XXX.
Luckily junk.txt was an LFN too.. or there'd be some splainin
to do.

That might get confusing to contemplate. Suppose a LFN file is deleted &
replaced a SFN file. If the SFN file is now deleted, I guess the slot
might be usable for a LFN.

If it requires the same or less number as the first LFN. The only thing
that compacts the directory structure is a defrag.

"PCR" wrote in message ...
Bill Blanton wrote:
"PCR" wrote in message
...
Bill Blanton wrote:

In DOS you can test this by doing
DIR /-o
DEL (some file in the middle)
COPY CON XXXXXXXXX.XXX (type a char, then F6)
Then do another DIR /-o

C:\dir windows\temp
...snip
NULLSO~1 DLL 59,392 03-18-09 9:57p NullsoftHelper.dll
JUNK TXT 110,592 03-17-07 9:23p junk.txt
CONTROL XML 12,818 07-07-09 6:06p control.xml
...snip

C:\dir windows\temp
...snip
NULLSO~1 DLL 59,392 03-18-09 9:57p NullsoftHelper.dll
XXXXXX~1 XXX 1 08-22-09 12:06a XXXXXXXXX.XXX
CONTROL XML 12,818 07-07-09 6:06p control.xml
...snip

You could also confirm that in a disk editor.

I'm happy enough as is.

I just noticed that you created a long name XXXXXXXXX.XXX.
Luckily junk.txt was an LFN too.. or there'd be some splainin
to do.

That might get confusing to contemplate. Suppose a LFN file is deleted &
replaced a SFN file. If the SFN file is now deleted, I guess the slot
might be usable for a LFN.

If it requires the same or less number as the first LFN. The only thing
that compacts the directory structure is a defrag.

Bill Blanton wrote:
"PCR" wrote in message
...
Bill Blanton wrote:
"PCR" wrote in message
...
Bill Blanton wrote:

In DOS you can test this by doing
DIR /-o
DEL (some file in the middle)
COPY CON XXXXXXXXX.XXX (type a char, then F6)
Then do another DIR /-o

C:\dir windows\temp
...snip
NULLSO~1 DLL 59,392 03-18-09 9:57p NullsoftHelper.dll
JUNK TXT 110,592 03-17-07 9:23p junk.txt
CONTROL XML 12,818 07-07-09 6:06p control.xml
...snip

C:\dir windows\temp
...snip
NULLSO~1 DLL 59,392 03-18-09 9:57p NullsoftHelper.dll
XXXXXX~1 XXX 1 08-22-09 12:06a XXXXXXXXX.XXX
CONTROL XML 12,818 07-07-09 6:06p control.xml
...snip

You could also confirm that in a disk editor.

I'm happy enough as is.

I just noticed that you created a long name XXXXXXXXX.XXX.
Luckily junk.txt was an LFN too.. or there'd be some splainin
to do.

That might get confusing to contemplate. Suppose a LFN file is
deleted & replaced a SFN file. If the SFN file is now deleted, I
guess the slot might be usable for a LFN.

If it requires the same or less number as the first LFN.

So that's another element of unpredictability as to whether a deleted
file will be there when one goes looking.

The only
thing
that compacts the directory structure is a defrag.

Right. Restoration can no longer find deleted files after a Defrag-- at
least, not the "regular" ones. It has a box to check to "include used
clusters by other files". I sense that option is scanning the hard drive
& doesn't depend on directories or even the FAT tables. It finds things
like "lears it.sel", "snipped.or", "he parti.tio". Let's see what one
of those looks like... plain junk!


--
Thanks or Good Luck,
There may be humor in this post, and,
Naturally, you will not sue,
Should things get worse after this,
PCR

Bill Blanton wrote:
"PCR" wrote in message
...
Bill Blanton wrote:
"PCR" wrote in message
...
Bill Blanton wrote:

In DOS you can test this by doing
DIR /-o
DEL (some file in the middle)
COPY CON XXXXXXXXX.XXX (type a char, then F6)
Then do another DIR /-o

C:\dir windows\temp
...snip
NULLSO~1 DLL 59,392 03-18-09 9:57p NullsoftHelper.dll
JUNK TXT 110,592 03-17-07 9:23p junk.txt
CONTROL XML 12,818 07-07-09 6:06p control.xml
...snip

C:\dir windows\temp
...snip
NULLSO~1 DLL 59,392 03-18-09 9:57p NullsoftHelper.dll
XXXXXX~1 XXX 1 08-22-09 12:06a XXXXXXXXX.XXX
CONTROL XML 12,818 07-07-09 6:06p control.xml
...snip

You could also confirm that in a disk editor.

I'm happy enough as is.

I just noticed that you created a long name XXXXXXXXX.XXX.
Luckily junk.txt was an LFN too.. or there'd be some splainin
to do.

That might get confusing to contemplate. Suppose a LFN file is
deleted & replaced a SFN file. If the SFN file is now deleted, I
guess the slot might be usable for a LFN.

If it requires the same or less number as the first LFN.

So that's another element of unpredictability as to whether a deleted
file will be there when one goes looking.

The only
thing
that compacts the directory structure is a defrag.

Right. Restoration can no longer find deleted files after a Defrag-- at
least, not the "regular" ones. It has a box to check to "include used
clusters by other files". I sense that option is scanning the hard drive
& doesn't depend on directories or even the FAT tables. It finds things
like "lears it.sel", "snipped.or", "he parti.tio". Let's see what one
of those looks like... plain junk!


--
Thanks or Good Luck,
There may be humor in this post, and,
Naturally, you will not sue,
Should things get worse after this,
PCR