Hi Anna,
> P.S. Wonder why terms like i386 are still being used for folders - 386
> machines were long ago.
Yes how to confuse the business :)
Initially used for Intel 386 processor based machines,
the term I386 - while outdated - is still being used to indicate Windows
based Software and hardware.
I586 is being used for Linux software.
As to your other questions: Rather than me explaining it,
you'll find answers to most if not all of your questions in the articles
at the links below (plus additional info)
http://ask-leo.com/can_i_move_or_delete_my_i386_directory_to_free_up_some_space.html
http://ask-leo.com/how_do_i_tell_windows_where_my_i386_folder_has_moved.html
How to install Widows from the I386 folder
http://www.easydesksoftware.com/I386.htm
http://www.petri.co.il/change_default_location_of_the_i386_folder.htm
Compress the ServicePackFiles\i386 folder in Windows XP
http://articles.techrepublic.com.com/5100-10878_11-5816838.html
This should give you a better understanding of the concept.
Further explanation: The reason why some people don't have the C:\I386
folder (full - as in a full copy of the one on the CD)
- the installation was not done from this folder,but instead was made
from the CD via the CD drive.
Some OEM CDs contain an install script that deletes the (copied)
installation files during a post-install cleanup.
During an install from CD ,the files from the I386 folder are copied to
a folder - sometimes C:\$WIN_NT$ or C:\I386 depending on the brand.
The contents is then extracted - mostly to C:\WINDOWS and sub folders
The cleanup procedure deletes the copied files from the initially
created folder.
> Is the i386 folder maybe where some OEM's put their mobo
> drivers?
Yes,sometimes they do.Sometimes they don't and have a dedicated folder
for this. IBM eg uses this type of setup.
Eg ,I have a large I386 folder under ServicePackFiles
The reason is that I started with XP straight -no service packs.
subsequent updates - SP1 and SP2 displaced the original files which are
now in this I386 folder. (one of the links above covers that)
Peter E.
-------- Original Message --------
Subject: Re: [PCSOFT] Slow Computer
From: g.Computer9f <[log in to unmask]>
To: [log in to unmask]
Date: 21-Jun-2008 5:11:20 PM
I was curious and checked my drive.
There is a C:\Drivers\ that contains ONE display driver and ONE USB
device driver ONLY (that are visible, at least).
The only i386 folders that Search (with hidden, system, protected etc.
all enabled to view) finds on
my HDD are.... C:\WINDOWS\System32\spool\XPSEP\i386\
...and... C:\WINDOWS\Driver Cache\i386\
The first folder contains only two files: mxdwdrv.dll and xpssvcs.dll
(an exact duplicate of which is also contained in it's parent folder)
The second folder folder (and its parent folder) are both invisible
unless I set protected system files to be viewable (after being warned
not to do so). The i386 folder contains ONLY two (visible) files:
driver.cab and sp2.cab which I didn't try to look inside of.
There are several (.sys) FILES containing the characters "i386" in five
folders that each look like....
C:\WINDOWS\system32\ReinstallBackups\000?\DriverFiles\*.sys
"i386" shows up in Search as a folder inside the (*.sys) files. Confusing.
What does it expect to see in the C:\i386 folder? This machine was
self-built with a retail copy of XP SP2 - is this why the folders are
different perhaps? Is the i386 folder maybe where some OEM's put their
mobo drivers?
AnnaSummers
P.S. Wonder why terms like i386 are still being used for folders - 386
machines were long ago.
PCSOFT's List Owner's:
Bob Wright<[log in to unmask]>
Mark Rode<[log in to unmask]>
|
