Windows 98 issues with SATA drive on VIA KT600

[jumper]

Drag-And-Drop is COPY!!!!!! Via "Temp" Folder! Period!

Yes, we are talking about file-based cloning. Beyond that, I fail to see how this is relevant to my question.

I'm not asking anyone to do any tests, I'm just wondering if anyone actually knows.

When I get some time, I'll put some files with long names (that have conflicting short names) on my ramdisk and clone it to a flash drive (or floppy or another ramdisk) using this drag-and-drop, icon-to-icon method. If all names match (long and short), I'll do some renaming and retesting in an effort to get it to fail.

Slow method? Yes. Easy method? Yes (if it works). Third-party app required? No--just what's already there.

[dencorso]

One of the things that are not guaranteed, when one does plain copy, is whether the short filenames created on copy will be associated to the same long-filenames as they are in the original source. This problem is well discussed in one of the XXCOPY knowledge base documents I gave a link to in one of my previous posts to this thread. Then there's the question of how hidden and super-hidden files will be treated...

[rloew]

Drag-And-Drop is COPY!!!!!! Via "Temp" Folder! Period!

Yes, we are talking about file-based cloning. Beyond that, I fail to see how this is relevant to my question.

I'm not asking anyone to do any tests, I'm just wondering if anyone actually knows.

When I get some time, I'll put some files with long names (that have conflicting short names) on my ramdisk and clone it to a flash drive (or floppy or another ramdisk) using this drag-and-drop, icon-to-icon method. If all names match (long and short), I'll do some renaming and retesting in an effort to get it to fail.

Slow method? Yes. Easy method? Yes (if it works). Third-party app required? No--just what's already there.

Not only is it necessary to create conflicting short names to get ~2, ~3 etc. but they have to be out of order in the Directory so that xxxxxx~2 comes before xxxxxx~1 in an unsorted Directory.

The following should do the job:

1. Create a new Folder x

2. Copy a file to x\aaaaaaaaa1.

3. Copy a file to x\aaaaaaaaa2.

4. Copy a file to x\aaaaaaaaa3.

5. Delete file x\aaaaaaaaa1.

6. Delete file x\aaaaaaaaa2.

7. Copy a file to x\bbbbbbbbb.

8. Copy a file to x\aaaaaaaaa2.

9. Copy a file to x\aaaaaaaaa1.

The source file can be anything, preferably small.

[jaclaz]

When I get some time, I'll put some files with long names (that have conflicting short names) on my ramdisk and clone it to a flash drive (or floppy or another ramdisk) using this drag-and-drop, icon-to-icon method. If all names match (long and short), I'll do some renaming and retesting in an effort to get it to fail.

With all due respect , a rather pointless experiment.

The idea is (was) to "clone" a drive where a bootable Win 9x OS was residing to another drive and have this latter boot that OS "as before".

Copying a bunch of files to a ramdisk is - even if sudccessful - only a subset of the needed chores.

Slow method? Yes. Easy method? Yes (if it works). Third-party app required? No--just what's already there.

As said, a lot of time have passed, so I cannot remember the details, but at the time the XCOPY approach already posted was used because no third party tools were needed and because the simple COPY did not work, AFAICR.

jaclaz