There are directories, and there are folders.

Directories are logical structures in a file system, and they typically hold the actual files (or more accurately, the references to the files, but that’s a distinction for the file system talk).

Folders are an Explorer concept and are, according to Microsoft, more correctly called Shell Namespaces (but I like folders, so that’s what I’m going to use). While there’s normally a 1:1 ratio of directories to folders, there are folders without directories, and while exceedingly rare, there are directories without folders. The classic example of a folder without a directory would be the Control Panel, or your desktop. An example of a directory without a folder would be the $Recycle.bin, since attempting to navigate that in Explorer will dump you into the Recycle Bin (which is another folder without a directory).

If you’re questioning what Explorer is telling you about your file system (and you should), you need to check another, less “user friendly” shell. Thankfully, Windows comes with CMD, aka the Command Prompt (which is being phased out, but details!).

C:\Users\▜▙\Searches>dir /a
 Volume in drive C has no label.
 Volume Serial Number is 8E69-32A1

 Directory of C:\Users\▜▙\Searches

11/09/2016  04:27 PM    <DIR>          .
11/09/2016  04:27 PM    <DIR>          ..
11/09/2016  04:27 PM               524 desktop.ini
09/22/2016  08:27 PM               248 Everywhere.search-ms
09/22/2016  08:27 PM               248 Indexed Locations.search-ms
09/22/2016  08:28 PM               859 winrt--{S-1-5-21-1001}-.searchconnector-ms
               4 File(s)          1,879 bytes
               2 Dir(s)  29,417,353,216 bytes free

C:\Users\▜▙\Searches>type "Indexed Locations.search-ms"
<?xml version="1.0"?>
<persistedQuery version="1.0">
    <query>
        <kindList>
            <kind name="item"/>
        </kindList>
        <scope knownScopeID="{f60163ce-2b8d-458d-ab2c-40f215767514}" />
    </query>
</persistedQuery>

C:\Users\▜▙\Searches>

Note that “Searches” isn’t really adding anything that hasn’t been there since Vista, we now just have a view into the index database.

How To Ask Questions The Smart Way

I had 2x1Gb and 2x512GB of RAM. I had onboard NIC and Netgear FA311 NIC. All working well.

I upgraded to 4x2Gb and 2x1Gb. The Netgear NIC stopped working. Yellow explanation and Error Code 10 Driver could not start.

I have:
Reinstalled Drivers. No Change
Moved the NIC to a different slot. No Change.
Remove 2x1GB Ram. No Change.
Added /3GB and or /PAE to boot.ini. No Change.
Upgraded Dell Bios. (took 2 tries). No Change.
Removed all of the new Ram. Installed only the 2x1Gb (existing).
Reinstalled NIC drivers (had tried numerous time during above steps) and got network back. Original Ram. Not New Ram.

I then swapped the ram for the 2x2Gb (new) ram. Lost NIC again with same error code.
Reinstalled NIC drivers. No Change.

I had purchased a new NIC and will install that now to see what happens. Will let you know. But this deffinately appears to be a NIC vs RAM conflict.

Thanks
Raoul

Tell us more. What are the file types you are copying and are you using CD-R or CD-RW? You need to burn to CD-R on XP and you don’t format the CD’s first. If the files are already on CD-RW then burn them onto CD-R instead. Preferably Finalize the CD-R’s produced to ensure they are readable on any system, including W98.

EDIT:
We need more information. If they are “audio CD’s”, for example, then the files have to be produced (ripped) from them before transfer, or you use a CD copying program to produce them again on W98. The whole point about CDFS is that it is universal – nothing new (see third link below).

Always pop back and let us know the outcome – thanks

message edited by Derek

You have to be a little bit crazy to keep you from going insane.
This site is about helping people, lets keep it that way.