Saving to desktop doesn't work

* When you say "you can find it", where do you find it (what directory)
* Do you work stand-alone or connected to a network
* Can  you create a text doc on your desktop (Rightclick on desktop, New, Text document) ? Dos it stay there or is it gone after reboot?

Edited text of question

This problem can occur when the Auto Arrange Icons option is enabled. Mostly together with a very crowded desktop.
To solve this, disable Auto Arrange Icons option and/or clean up your desktop. (rightclick on desktop, Arrange Icons, Auto Arrange).
Hope this solves your problem.

I ALREADY SAID that I tried Auto Arrange.  THAT's NOT THE PROBLEM.  MY DESKTOP IS NOT VERY CROWDED.  I TRIED THIS FROM A CLEAN INSTALL.  I HAVE MAYBE SIX THINGS ON THE DESKTOP.  I HATE AUTO ARRANGE AND IT IS CERTAINLY NOT ENABLED.  DID YOU EVEN READ MY EDITED QUESTION?  I WANT MY POINTS BACK AGAIN.  THIS SITE SUCKS.  TWO QUESTIONS, NO ANSWERS.

Chris: You wouldn't have Internet Explorer 4.0 on your new system would you?

Best regards,
Dennis

No.  I don't have IE 4.0.  I don't have IE at all, because I did a clean reinstall and didn't load ANYTHING so I could test this problem.  It's even using the basic 640x480, 16 color default video driver.  This configuration is just Windows and nothing else.

<<<I ALREADY SAID that I tried Auto Arrange. THAT's NOT THE PROBLEM. MY DESKTOP IS NOT VERY CROWDED. I TRIED THIS FROM A CLEAN INSTALL. I HAVE MAYBE SIX THINGS ON THE DESKTOP. I HATE AUTO ARRANGE AND IT IS CERTAINLY NOT ENABLED. DID YOU EVEN READ MY EDITED QUESTION? I WANT MY POINTS BACK AGAIN. THIS SITE SUCKS. TWO QUESTIONS, NO ANSWERS. >>>
 
Nice attitude Chris99.  I know what the problem is, but tell me why I should give you the solution?

To jscrouch:

SUUUUUUUUURE you do.

What would your attitude be if you asked two questions to this site and both times got back answers which told you to do things that you've a.) already tried, and b.) mentioned in your question that you've already tried?

I'd be appreciative of people spending the time to try to help me.  No, you will not always get the right answer.  Yes, people will sometimes not re-read your edited question.  But everyone here is trying to help, and that's what you should be looking at.

PS - I had the same problem as you last week on my own computer and fixed it.  Sorry.

Chris, simply put, we get all sorts of people at this site, some very knowledgeable and some not so! We are not sitting in front of your computer, have no clue as to your capabilities, have no idea what your computer is made up of other than a Dell LX PII/266 and no idea what other software is on it or whether Windows 95 was loaded correctly or had a partial or completely failed load. Furthermore, if it has a TX, VX, FX or LX chipset, it may not have the PCI Bridge drivers, USB drivers or the LX chipset drivers loaded properly, let alone correct video drivers. Given that we are volunteers, the advice you receive is free but requires hours of research. There are alternative however, you can call Dell or Microsoft at $35.00 per incident.
Dennis

To everyone who took the time to read my question carefully and respond thoughtfully, I apologize deeply, sincerely, and from the bottom of my heart.  I challenge ANYONE to tell me how to fix this problem on my PC.  If anyone can, they can have a whole month's worth of "points", if that matters to anyone.  But what good is a site which offers help to you if they won't even read your question?  I went through the process of registering, picking a username, etc, in support of this site.  If anyone can answer this question, do it, and redeem this site!  If you can't, then fine, I'll go elsewhere.  I will be more than happy to answer any relevant question about what software is installed, whether or not it was complete, etc., etc.  Just tell me you need more information.

In answer to what you were wondering, yes, as far as I know, Windows 95 was loaded correctly.  There were no error messages on install, and nothing seemed out of the ordinary.  As for the PCI bridge drivers, I loaded them exactly according to Dell's instructions:  Load the Intel disk software.  Load the USB drivers.  Load the Intel disk software again.  There were no problems in doing this, no error messages, etc., so I can only assume that I did it correctly.

Is there any particular application where this is occuring, or is it any app all the time.

Any app, all the time.  Even Notepad.  I noticed it first in Netscape, because I usually download files to the desktop.  After downloading, I wouldn't see the file.

Have you tried just clicking on the desktop and pressing F5 ?

Consider a Shell utility like EZ-Desk. If it works, we know something is wrong in the shelliconcache or the registry.
http://www.voicenet.com/~phidelt/index2.htm
Free. Let me know what you think before I go on a rant about other utilities.
This site by the way is the "Windows 95 Help & Resource Center'.
Very good.

2nd, save your C:\Windows\ShellIconCache to a temporary directory, then delete it. It *Should* remake itself on re-boot into windows. If not, you have your backup.

One more thing, check your System Properties, Performance tab to see that you're running Not in MSDOS COMPATABLITY MODE.

To Mike P:  Yes, clicking on the desktop and pushing F5 makes the icon appear immediately.  What is F5?
But I still want the icon to appear on its own.  Thanks for a painless workaround, though.

To smeebud:  There's no mention of MSDOS compatibility mode in the system properties area (on the performance tab).
I downloaded EZ desk, which seemed to work fine.  With it running in the background, I opened a new notepad document and saved it to the desktop.  It still didn't show up.
I deleted the ShellIconCache and restarted.  It did make a new ShellIconCache, but I still couldn't a file to show up on the desktop immediately upon Save.  

Is there maybe a line in an .ini file or something that forces the desktop to regenerate itself constantly?  Or frequently?

F5 in Explorer is "refresh": re-read. Looks like your Explorer
couldn't catch changes atomatically, thus should be made to do it
manually. Mike gave a good hint, that leads to the root of problem.

Anyone have any ideas how to make it work?

In your registry see that your refresh is set as follows;I left my other setting there just for you to see.
I'd concern only with the Refresh rate

[HKEY_LOCAL_MACHINE\Config\0001\Display\Settings]
"fonts.fon"="vgasys.fon"
"fixedfon.fon"="vgafix.fon"
"oemfonts.fon"="vgaoem.fon"
"DPILogicalX"="96"
"DPILogicalY"="96"
"DPIPhysicalX"="96"
"DPIPhysicalY"="96"
"MouseTrails"="0"
"BitsPerPixel"="24"
"Resolution"="640,480"
"RefreshRate"="-1"
----------
[HKEY_LOCAL_MACHINE\System\CurrentControlSet\Services\Class\Display\0009\DEFAULT]
"Mode"="8,640,480"
"drv"="mgapdx64.drv"
"vdd"="*vdd,*vflatd"
"minivdd"="mgapdx64.vxd"
"RefreshRate"="-1"
"DDC"="1"
"CHIPID"=hex:00,00,00,00,00,00
------------------
[HKEY_CURRENT_CONFIG\Display\Settings]
"fonts.fon"="vgasys.fon"
"fixedfon.fon"="vgafix.fon"
"oemfonts.fon"="vgaoem.fon"
"DPILogicalX"="96"
"DPILogicalY"="96"
"DPIPhysicalX"="96"
"DPIPhysicalY"="96"
"MouseTrails"="0"
"BitsPerPixel"="24"
"Resolution"="640,480"
"RefreshRate"="-1"

Okay.  I did as you suggested.  In my registry, I have the same settings as you (-1) for the RefreshRate.  The only difference I can see is in the HKEY_LOCAL_MACHINE\System\
CurrentControlSet\Services\Class\Display part, I don't have
\0009\DEFAULT,
instead I have
\0001\DEFAULT,
and the RefreshRate there is also set to -1.

In case it's relevant, here are the exact settings.
                   [HKEY_LOCAL_MACHINE\Config\0001\Display\Settings]
                         "fonts.fon"="vgasys.fon"
                         "fixedfon.fon"="vgafix.fon"
                         "oemfonts.fon"="vgaoem.fon"
                         "DPILogicalX"="96"
                         "DPILogicalY"="96"
                         "DPIPhysicalX"="96"
                         "DPIPhysicalY"="96"
                         "BitsPerPixel"="32"
                         "Resolution"="1152,864"
                         "RefreshRate"="-1"
                         "DisplayFlags"="0"
                         ----------
                         [HKEY_LOCAL_MACHINE\System\CurrentControlSet\Services\Class\Display\0001\DEFAULT]
                         "Mode"="16,640,480"
                         "drv"="stbv128.drv"
                         "vdd"="*vdd"
                         "minivdd"="stbv128.vxd"
                         "RefreshRate"="-1"
                         "DDC"="1"
                         "CHIPID"=hex:67 45 23 01 00 00
                         "defaultdrv"="stbv128.drv"
                         "ResumeReset"="1"
                         ------------------
[HKEY_CURRENT_CONFIG\Display\Settings]
                         "fonts.fon"="vgasys.fon"
                         "fixedfon.fon"="vgafix.fon"
                         "oemfonts.fon"="vgaoem.fon"
                         "DPILogicalX"="96"
                         "DPILogicalY"="96"
                         "DPIPhysicalX"="96"
                         "DPIPhysicalY"="96"
                         "BitsPerPixel"="32"
                         "Resolution"="1152,864"
                         "RefreshRate"="-1"
                         "DisplayFlags"="0"

Any of this other stuff make any difference?

Thanks a LOT for your time.
Chris.

I doubt, that your problem is connected to Display/Video system at all.
I think that here is problem with Explorer settings. I'll investigate
it further.

Ian

Chris99,
Display could have everything to do with it. Please read the following carefully.
--------PART1
If there is a problem with a device, it is listed in the hardware tree
list under Computer. The problem device has a symbol indicating
the type of problem:

A black exclamation point (!) on a yellow field indicates the device
is in a problem state. A device in a problem state can be
functioning. A problem code explaining the problem is displayed
for the device.

A red "X" indicates a disabled device. A disabled device is a
device that is physically present in the system, consuming
resources, but does not have a protected-mode driver loaded.

A blue "i" on a white field on a device resource in Computer
properties
indicates that Use Automatic Settings is not selected for the device
and that the was manually selected. It does not indicate a problem
or disabled state.

NOTE: Some sound cards and video adapters do not report all
the resources they are using to Windows 95. This can cause
Device Manager to show only one device in conflict, or no
conflicts at all. This can be verified
by disabling the sound card, or using the standard VGA video
driver too see if the conflict is resolved. (This is a known problem
with S3 video cards and 16-bit Sound Blaster sound cards, or
those sound cards using Sound Blaster emulation for Sound
Blaster compatibility.)
When you select a specific device in Device Manager, then click
the Properties button, you see a property sheet. The property
sheet has a General tab.

NOTE: Some devices may have other tabs besides the General
tab.
Not all property sheets have the same tabs; some devices may
have a Resource tab, Driver tab, and Settings tab, or some
combination of these.

At the top of the property sheet, there is a description of the
device. When you click the Resource tab, the window in the
middle of the tab indicates which resource types are available for
the selected device.

The scroll box at the bottom of the contains a Conflicting Device
list.
This list indicates a conflict with an error code.
Note the Use Automatic Settings check box. If Windows 95
successfully detects a device, this check box is selected and the
device should function correctly.
However, if the resource settings are based on Basic Configuration
(where is any number from 0 to9), it may be necessary to change
the configuration by selecting a different basic configuration from
the list. If the particular configuration you want for the device is not
listed as a basic configuration, it may be possible to click the
Change Settings button to manually adjust the resource values.

For example, to edit the Input/Output Range setting, use these
steps:
1. Click the Use Automatic Settings check box to clear it.
2. Click the Change Setting button.
3. Click the appropriate I/O range for the device.

Please see:
http://www.microsoft.com/support/tshoot/w95startup.HTM 
                    Return to Top
                         
         MAKE A LIST AND PRINT IT TWICE
A printout of your system settings is a good reference to keep
handy for hardware troubleshooting. Right-mouse click on My
Computer, select Properties, and click on the Device Manager
tab.
Click on Print, choose the type of report you'd like to print, and
click on OK.
"System summary" prints a report organized by resource type--
IRQ, I/O port, memory, and DMA channel--listing the hardware
that uses each resource. (Double-click on Computer back on the
Device Manager tab to view this information on-screen.) "Selected
class or device" lists the resources and any device drivers used by
the selected hardware. Of course, you'll need to select the
hardware before clicking on Print. And the third option, "All
devices and system summary," prints a system summary and details
for every piece of hardware on your system.
                    Return to Top
                         

USING THE DEVICE MANAGER EFFICIENTLY
If a hard ware such as a mouse, modem or CD-ROM didn't get
detected automatically and you know that CMOS settings and the
hardware is OK then you could have IRQ or I/O port conflict.
The best way to find out is go to the Control Panel\System
icon\Device manager tab and click print, don't select to print the
whole report because you will end up with 40 pages or more, just
select the IRQ and I/O ports summary, from there you see what
using what.
---------------PART2

Article ID: Q127139

This article describes how to troubleshoot video display problems
or error messages relating to the video display driver when you are
starting or using Windows 95.

MORE INFORMATION

Video problems that occur when Windows 95 is started normally,
but do not occur when Windows 95 is started in Safe mode are
usually related to the display driver that Windows 95 is attempting
to use. To determine whether you are using a Windows 3.1 or
Windows 95 video driver, follow these steps:

1. Use any text editor (such as Notepad) to open the System.ini
file in the Windows folder.

2. In the [Boot] section, search for the "Display=" line. If this line
reads anything other than the following line, the driver you are using
is designed for Windows 3.1 (or an earlier version of Windows):

Display.drv=Pnpdrvr.drv

If you are using a video driver designed for Windows 95, go to the
"Advanced Graphics Settings" section in this article. Otherwise,
continue with the following section.

Windows 3.1 Display Drivers

If no Windows 95 display driver is available for your video
adapter, try using the Windows 3.1 drivers available from the
adapter's manufacturer. Consult the documentation included with
that driver for information about how to install the driver.

NOTE: If you use a Windows 3.1 display driver in Windows 95,
you cannot use new Graphics Device Interface (GDI) features
such as:

* Animated cursors. For information about using animated cursors,
please see the following article in the Microsoft Knowledge Base:

ARTICLE-ID: Q123334

TITLE : Requirements for Animated Cursors

* Dynamic resolution changes. In many circumstances, you can
change the video resolution in Windows 95 without restarting
Windows 95. If you change the color depth or the video driver
you are using, you must restart Windows 95. * VGA fallback
mode. If Windows 95 detects a problem with the video card or
video driver, it restarts with the VGA driver. * The Windows 95
virtual flat frame buffer device (Vflatd.vxd). Vflatd.vxd provides a
frame buffer that can be up to 1 MB in size. Windows 3.1 video
drivers are limited to a 64K frame buffer that affects your available
system resources.

If the Windows 3.1 display driver does not work properly in
Windows 95, use the standard VGA driver included with
Windows 95. To do so, follow these steps:

1. In Control Panel, double-click Display.

2. Click the Settings tab, and then click Change Display Type.

3. Click the Change button in the Adapter Type section, and then
click Show All Devices.

4. In the Manufacturers box, click (Standard Display Types).

5. In the Models box, click Standard Display Adapter (VGA),
click OK, and then click Close.

6. Click Close.

If you continue to experience problems, continue with the following
section.

Advanced Graphics Settings

Windows 95 has a built-in method for troubleshooting video
problems. There is a slider you can adjust to change the way
Windows 95 uses the video card. It is a good idea to start with the
setting on the right (the Full setting) and move the slider one setting
to the left until you find the setting that works best. To use the
slider to change the way Windows 95 uses the video card, follow
these steps:

1. In Control Panel, double-click System.

2. Click the Performance tab, and then click the Graphics.

3. Note that the Hardware Acceleration slider has four settings
(Full, Most, Basic, and None). Each of these settings is described
below.

- Full

This is the default setting and allows for full hardware acceleration.

- Most:

This setting adds the following items:

- SWCursor=1 to the [Display] section of the System.ini file.

Setting SWCursor to 1 disables the hardware cursor.

NOTE: This setting is similar to using the /Y switch with some
versions of the MS-DOS-level Microsoft Mouse driver.

The Most setting applies to Western Digital (WD) or
S3-compatible drivers. If you have problems with the way the
mouse pointer appears on the screen, try this setting.

- Basic:

This setting adds the following items:

- SafeMode=1 to the [Windows] section of the Win.ini file.

Setting SafeMode to 1 allows for basic acceleration only (for
example, pattern bit block transfer [bitblt] and screen-to-screen
bitblt).

- MMIO=0 to the [Display] section of the System.ini file.

Setting MMIO to 0 disables memory-mapped I/O for
S3-compatible drivers.

- SWCursor=1 to the [Display] section of the System.ini file.

Setting SWCursor to 1 disables the hardware cursor.

Try the Basic setting if your computer seems to stop responding
(hang) randomly and you have an S3-compatible video driver.

- None:

This setting adds the following items:

- SafeMode=2 to the [Windows] section of the Win.ini file.

Setting SafeMode to 2 disables all video card acceleration (for
example, the GDI calls the device-independent bitmap [DIB]
engine directly for screen drawing, rather than using the display
driver).

- MMIO=0 to the [Display] section of the System.ini file.

Setting MMIO to 0 disables memory-mapped I/O for
S3-compatible drivers.

- SWCursor=1 to the [Display] section of the System.ini file.

Setting SWCursor to 1 disables the hardware cursor.

Try the None setting if your computer seems to hang randomly,
you have an S3-compatible video driver, and the Basic setting
does not resolve the problem.

If you continue to experience problems, continue with the following
section.

Monitors

Use the following steps to verify that your monitor is selected
correctly in Windows 95.

WARNING: It is possible to cause damage to your monitor if you
select a monitor type that exceeds the capabilities of your monitor.
Consult the monitor's documentation or manufacturer for specific
information about its capabilities.

1. In Control Panel, double-click Display.

2. Click the Settings tab, and then click Change Display Type.

3. Click the Change button in the Monitor Type section, and then
click Show All Devices.

4. In the Manufacturers box, click the manufacturer of your
monitor.

NOTE: If your monitor's manufacturer is not listed, click (Standard
Monitor Types).

5. In the Models box, click the monitor you are using, click OK,
and then click Close.

6. Click OK.

If you continue to experience problems, continue with the following
section.

Eliminate Memory Conflicts

Determine whether the problem is a result of a conflicting driver in
memory. For information about how to do so, please see the
following article in the Microsoft Knowledge Base:

Article-ID: Q136337 Title : Troubleshooting Windows 95 Startup
Problems and Error Messages

If you continue to experience problems, continue with the following
section.

Verify Valid Driver Files

To verify that the display adapter driver files are valid, run
Windows 95 Setup again and choose the Verify option when you
are prompted. The Verify option causes Windows 95 to check all
files and replace any that are missing or damaged.

If you continue to experience problems, continue with the following
section.

Contact the Manufacturer of the Display Adapter

If none of these troubleshooting steps correct the problem, contact
the display adapter's manufacturer for information about obtaining
an updated Windows 95 driver.

REFERENCES

For additional information about display adapters and switches that
correct some display problems, please see the following article in
the Microsoft Knowledge Base:

ARTICLE-ID: Q124267 TITLE : Display Adapter Information
and Useful

To Smeebud:  I looked in the list of devices and none of them was showing a conflict icon as you described.  However, I went into the Resources tab of the graphics card and there were two memory address conflicts with a PCI to PCI adapter.  So I clicked on change settings for the video card and clicked on the next available memory addresses that said no conflicts, and restarted.  When I restarted, it told me there was a problem with my graphics adapter and started in VGA mode.  When I tried to go into change settings to set it back to Automatic, the computer locked up and I had to reset it.  This happened about four times.  I formatted C (again) and am going to reinstall Windows 95 tonight.  I'll post the results ASAP.

Chris99...

You didn't have to reformat your hard drive.  We could have saved you a long trip.

Anyway, good luck!
Regards

Hey, man, installing Windows 95 is second nature to me now.  I don't even have to think about it.

Good for you.
I recommend to all my clients to do it every 6 months, BUT they can of... (you figure it out)
Regards

Wow,
After you re-install, see that you have in your system.ini
[386Enh]
display=*vdd,*vflatd

Then reflect that in your registry. I noticed you did not have at
[HKEY_LOCAL_MACHINE\System\CurrentControlSet\Services\Class\Display\0001\DEFAULT]

"vdd"="*vdd" [HERE, SHOULD BE "vdd"="*vdd,*vflatd"]

Chris: Did Dell give you the drivers for the LX chipset?

Yes, I believe so.  They gave me a disk called Intel-something-something Update or something like that.  I'm supposed to install the update immediately after installing Windows, then install USB support, then install the update again.

Chris: There's a finite way to install those drivers. If Dell hasn't been clear on how they should be installed, let me know and I'll post it for you.
Dennis

Chris99,
I stressed the
VFLATD    Linear Frame Buffer Video Driver
because I believe you problem is display related. This one sparked my intrest so i've been researching and still am.
So with thoses changes and this final suggestion, I'll mark this answered. of course if it doesn't work, Reject.
=======
Some IDE hard drive controllers don't seem to allow the full 32-bit optimal performance, thus forcing compatibility mode. I found a trick that will fix this problem: RUN REGEDIT.EXE and find NOIDE when you find it, right click on it and change it's value from 01 to 00. When this is done close REGEDIT and restart your Windows. This has came in very handy many times. Much faster performance than before. Not only that, brings back your animated cursors and lost drives. It helps the system a lot.
============
Please post results.

Well, the documentation they provided told me this:  
Immediately after a Windows 95 install, insert the Intel update disk.  Run setup.  (I do this and it installs some things, restarts a time or two, and stops.)
Then it tells me to insert the W95 CD-ROM they provided and go to a folder and run a USB .exe program to install USB support.  (Which also restarts the computer.)
Then it tells me to insert the Intel update disk again and run setup.  (It restarts and finds a lot of new stuff and restarts again.)
If this is incorrect, let me know, but this is all they told me in their documentation.  And I followed it to the letter.

Chris.

Is the problem realy so big that it worth spending so much time solving it? Why not just press F5 and that's it?

MikeP,
Because it ain't right.

Bud: I like your answer, but it doesn't solve the problem on an LX board. It has nothing at all to do with VFLATD Linear Frame Buffer Video Driver. The LX chipset is new to Windows 95. The retail version has not provisions for it at all, and only OSR2 releases after May 1997 with the supplement address some of the features and "you must use the Intel drivers disk" as it employees the new chipset architecture. With incorrect or imporper drivers installed, Windows 95 permits hidden IRQ and DMA channel shadowing. The LX, like it's cousin the TX and FX,  create shadow conflicts that Windows 95 does not reflect in Device Manager as a conflict or disabled device. Simply put, it drives windows crazy trying to sort out the devices. One will work one day, while not work another after a restart. There is only one way to correct it, and that's a finite order of installation.
Dennis

Smeebud:  Exactly!  Because it's not right.  Thank you.

Dennis:   I hear what you're saying about order of installation.  Am I doing it in the wrong order?

Wow,
Computers are getting more complex every minute.
I see great opportunities ahead; profession installers and uninstallers for example. ::))
I smile and jest but it's viable.

Chris: Here is the order of install for WIN95 on an LX board. It's realtively easy as long as you pay attention to what is going on in device manager as you go through the process. Obviously you have already Fdisk'd the drive and formatted it, however I will take you through the process, from beginning to end on a clean hard drive. This presumes that you have (A) Windows 95 OSR2 (B) the OSR2 Supplement (C) the Intel Bus Master Drivers on floppy or CD and (D) you have the LX Chipset drivers either on floppy or CD.

1. Fdisk the driver and enable LBA if desired (you will see a difference with Fast ATA drives and the new chipset if you use LBA on drives over 2.5G)

2. Format Drive "C" and transfer the system files, including Himem.sys, *******.sys and Mscdex.exe for cd rom drive and Himem.sys. Setup real mode CD Rom drivers and Himem.sys in Config.sys and Auroexec.bat.

3. Load Windows 95, but instead of typical install, use custom and choose only those components that you will use.

4. After Windows 95 has finished it's final restart, check device manager. Device Manager should show that there is a problem on the IDE Bus, the PCI to PCI Bridge as well as USB.

5. Next, load the Bus Mastering Drivers for your motherboard. Don't be concerned about DMA/UDMA support or check boxes for the drives, there won't be any. OSR2 and the new drivers for the LX chipset disables turning on or off DMA for hard drives as it employs full time support along with SMART drive.

DO NOT let the system reboot after these Bus Mastering Drivers are loaded unless your not given a choice!

After you have loaded the drivers, go to Device Manager and scroll down the list until you come to the entries for devices that have conflicts, such as PCI to PCI, USB and the IDE Bus. Highlight them all and delete them.

Then, scroll to the Hard Disk Controller and click on the "+" sign and expand it. Highlight the entries and click remove. This may lockup the system but don't worry about it. Now you can restart the system. As it boots, it will find the IDE Bus and begin sorting out the conflicts with the LX chipset. After the devices have been found (if everything works properly) it will find the master bus and the Primary controller and then ask for a restart. (Note: it may also find the secondary bus depending how Dell wrote the batch file) On the restart, the secondary bus may be found, or it may have loaded with the primary. Go to device manager and verify that you have them listed like this:

Intel PIIX/PIIX3 Bus Master IDE Controller
Primary IDE Controller
Secondary IDE Controller

Note: The PIIX/PIIX3  can also be shown as PIIX4

If the appear as above, go on. If not, remove the bus entry and restart the system.

6. The next item is the PCI to PCI Bridge that the LX chipset builds. The Dell disk may load this along with the Bus Mastering and it may not. If you still have a conflict for this device, you will have to load it manually.

In Device Manager, remove the entry and close device manager and reboot. If windows find it, do not let windows use its own driver, point it to the floppy or cd that Dell provided. You may have to spend a few minutes wading through their directories, but it's there and Windows will recognize it based upon the LX chipset reporting its identity. When this has loaded and you have verified that it is correct and without conflict, then move on to the USB support.

7. USB support installation is arbitrary. If you have the ports on the machine, then load the supplement like any other Windows update, like this.

A. Transfer the supplement to an empty Temp file on your hard drive.

B. Go to Device Manager and find the USB port, it should show that the device is unknown. Expand it if necessary and remove it. Close Device Manager, then..

C. Use "ctrl"  "alt"  and "del" and open the "Close Programs" dialogue box and close all running programs EXCEPT for Systray and Explorer.

D. Use Find, Files and Folders to find the supplement. After it has been installed, restart the computer. It should find the device and install it. However!!! Windows tends to get stupid and forgets where it put the support files. If it can't locate it, point it to C:\Windows\System.

8. Last but not least, you don't mention whether your video card is standard PCI or AGP/PCI in its own bus. Either way, now is the time to add either your regular video drivers or your AGP (Advanced Graphics Port) drivers and then your video drivers.

Let me know how you make out, and whether there are any questions!

Best regards,
Dennis

One thing to add: to avoid possible conficts, and because I don't
have ANY USB devices, I disabled it through BIOS Setup and Win95
not found this thing at all upon installation. I suggest you to
do the same, unless you have USB devices <g>.

Ian

I'm back to the original question. I've been studying this for days looking for answers. Here comes my new addition to my database. Please give it a go and let me know:)
----------
The icons that windows95 uses on the desktop and elsewhere
are stored in a file named shelliconcache.  The default limit
which MS uses is too low.  Hence, when you introduce a new
icon to the system by opening a new folder, etc., the cache
is dumped and rebuilt.  You can test this yourself by opening
several instances of explorer at different folders.  The
desktop will refresh when the limit is reached. To solve the
problem, edit the registry to increase the default maximum
number of icons stored in the cache.  Here is my Registry
Export file to accomplish this.  It increases the default to
8000 icons. You can experiment with that "8000" value.
----------------
REGEDIT4

[HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\Windows\CurrentVersion\explorer]
"Max Cached Icons"="8000"
----------------

Ian: Disabling the USB bus may very well be an option for you because of the structure of your system, however there are bridge issues built into the LX chipset that makes merely disabling the USB ports ill advised unless there is a specific hardware problem that cannot be resolved in another manner.
I know everyone is search for answers for Chris, however it think it would be prudent to first get him to a stable system environment with eberything working then move on to other issues such a saving to a desktop. We've strayed all over the map here, but I think we all believe that when a new system doesn't do somthing it should, it's either a hardware issue or bad install, and the place to start is with the hardware and come forward to a rock solid system.
Dennis

Smeebud:  I looked in the registry for MaxCachedIcons and it wasn't there.  So, in the directory you told me, I added a new value called that, and set it at 8000.  I restarted.  Still no success.  So I deleted it to get the registry back to its initial state.

Dennis, I'm now going to try to reinstall according to your instructions.  I hope I have all the disks I need.

Okay, Dennis, I went through your list.

I started by formatting C:.  I didn't fdisk, because I had a D: and E: drive with information still in it.  I started the install of Windows.  I installed the componenets I wanted.  After it was done, I checked for conflicts.  The only conflict was the PCI to PCI bridge which was conflicting with the standard VGA driver.  I installed the Intel 82371xB INF file updater, which I presume has the Bus Mastering Drivers.  I did not reboot after this was done, I went to the PCI to PCI bridge, which still had a conflict, and deleted it.  Then I removed the only entry under Hard Disk controller.  Then I restarted.

I checked device manager and saw that the controllers were listed as you described, except instead of Intel PIIx/PIIx3 Bus Master IDE Controller, it was listed as Intel 82371xb Bus Master IDE Controller.  I presume this is okay.

I couldn't see the PCI to PCI bridge being built.  I checked it after it was done and there was still a conflict.  I removed it, rebooted, and whenever I was asked for a file, I directed it to the boot disk.  It could never find a file, so I just let it keep whatever it had already found.  The install disk that Dell gave me had no files on it other than a Setup program.  I opened device manager again and the PCI to PCI bridge conflict was still there.  I don't know what else to do.

I loaded the USB support, no problem.  

The video card is an STV Velocity 128 (OEM version) and is an AGP card.  As for AGP drivers, Dell did not supply me with a disk with AGP drivers, as far as I can tell.  The only files on the STB CD are nv3api.dll, nv3rm.vxd, nv3sys.dll, readme, stbv128.drv, stbv128.inf, stbv128.vxd, stbv128d.dll, and vgartd.vxd.  Is there supposed to be a separate AGP driver disk?

So in summary, I couldn't do a lot of the stuff you told me to, and as a result, the conflicts are still there.  (By the way, so is the saving to desktop problem.)

Chris.

Chris: You did real well, so don't worry about it. What you have left can be easily done with some work.

Let's deal with the PCI Bridge first:
-----------------------------
1. Go to device manager and remove it.

2. Restart Windows 95 and when windows finds the PCI Bridge and asks for the file, point windows to:

       C:\Windows\System

In all probabilty Dell's disk installed the driver there.

3. Check device manager and let me know if there's still a conflict. If there is, you'll have to get the actual driver from Dell, although I believe it is available on the Intel site as well.


If all is well, then try reinstalling the AGP card. You won't be able to install this correctly until the PCI to PCI bridge is done.

As for the PCI/AGP card, try this.

1. Go to control panel and display properties, click settings then change display type then click change adapter.

2. Use "Have Disk" and use the disk that you have the stbv128.drv, stbv128.inf, stbv128.vxd, stbv128d.dll, and vgartd.vxd drivers on.

3. You should be able to restart your system and the AGP card should be functional.

Hopefully when you reply, everything will have gone well and you have a stable system, then we can try and deal with the desktop issue.

Again, well done!
Dennis


2.

Thanks, Dennis, I'll try again tonight.
Thanks, Smeebud, for your suggestions.  I still couldn't find the  NOIDE section of the registry.  Should I add this key?  If so, where?

Thanks again.
Chris.

HKEY_LOCAL_MACHINE\SYSTEM\CURRENTCONTROLSET\SERVICE\VXD\IOS

There make your "String value key" NIODE=00
  Of course, before doing this, the registry should be backed up in such a way that you are sure you can recover it if needed.

Smeebud:  In the registry section you specified, my current values are
Start 00
StaticVxD "*IOS".

I added
NOIDE "00"
and restarted.

I tried to save to desktop again with no luck.

Some have suggested that I might have bad memory, but I did Dell's diagnostics on my system and both RAM and hard drive checked out okay, for what that's worth.

Thanks,
Chris.

Chris: Try and find out which chipset the PCI bridge is using. It should still be the TX family even though the IDE and DMA bus is using the LX chipset. If it's not in your Dell documents, give me the exact model info and I'll get the info for you as well as identify the file(s) for you. Until that PCI bridge is reconciled, you won't be able to resolve the AGP video slot on the bus.
Dennis

I just followed another thread, I got some hint from it. Chris,
what programs you have on startup (I mean Systray) ? Do you have
some kind of desk from STB ? Try to remove it.

I'll check the documentation tonight.  The computer is a Dell Dimension XPS D266.  I have heard other people in the Dell newsgroup say the same thing about having conflicts.  Maybe Dell's update program doesn't perform quite right?

To Busuka:  STB has nothing that loads on startup.  These are very basic drivers.  I had loaded some of their driver updates, one of which included Vision 98, but I haven't loaded that driver set since my 11,000th reinstall.

I have tried to answer your question before, but have been locked out.  I think that you need to check your windows desktop directory and check under profiles.  If you have a profile for another user name, it could be saving your items there.  I would suggest that you rename the *.pwl files on your computer, log in under a new username, set a password or not, your preference, and then delete any user profiles under any other user name than the one you just set.  Of course before doing that, copy any items you want on your new user name desktop to that profiles desktop first.  
Kent
kencam@pobox.com

A better way to check ram
-------
Ram Checkers Don't Always Find Bad Ram Chips. Unless
memory Chips are extremely faulty, checking programs are not
adequate tests because they do not test RAM in the same way that
Windows uses RAM. Memory checkers use read/write cycles.
Since Windows is executing code from memory, it uses execute
cycles. Execute cycles are different from read/write cycles and are
more vulnerable to parity errors. Bad memory chips can also cause
the following situations:
1. Fatal Exception errors.
2. Himem.sys load failures in normal or Safe mode.
3. Random lockups.
4. The computer may stop responding (hang) as soon as you turn it
on.
Remove or replace memory chips in the computer to see if the
problem is resolved.
Try limiting the amount of memory that Windows 95 uses. To do
so, follow these steps:
1. Use any text editor, such as Notepad to edit the System.ini file.
2. Add the following line in the (386Enh) section of the file:
MaxPhysPage=< nnn > where < nnn > determines the amount of
memory you want Win95 to use.
To limit Windows 95 to the first 4 MB of memory, add the
following line: MaxPhysPage=3FF
To limit Windows 95 to the first 8 MB of memory, add the
following line: MaxPhysPage=7FF
To limit Windows 95 to the first 16 MB of memory, add the
following line: MaxPhysPage=FFF
3. Save and then close the System.ini file.
4. Restart your computer. Check how it runs. If OK, then test the
next, i.e.; 8MG

An edit to my proposed answer, profiles are under the Windows directory, not desktop.  Should be c:\windows\profiles\username ,if you do not have a profiles directory, then you do not have windows set for multiple users and this answer won't apply.  If you do have profiles, then there are desktops in there for all registered users.  You can check password properties as well under control panel, and this will tell how your system is currently configured for profiles.

Kent's idea has merit, I'd like to follow up on it with a ittle more detail:
---------------
Create and Enable User Profile
To enable user profiles on a local computer after setup
1. In the Passwords option in Control Panel, click
the User Profiles tab.
2. Click to select the option named Users Can Customize
Their Preferences And Desktop Settings.
3. Click the options you want under User Profile Settings.
These options describe what should be included as part of
the user profile.
4. Shut down and restart the computer.

Tip If you include desktop icons in your user profile,
only the shortcuts (icons that represent links) will be
available when you log on to the network from another
computer. Actual files on your desktop are part of your
local user profile only.

To disable user profiles on a local computer

In the Passwords option in Control Panel, click the User
Profiles tab. Make sure the option named All Users Of
This PC Use The Same Preferences And Desktop Settings is
selected.

Note:  If an application is installed after user profiles
are enabled with the option to include the Start menu and
Programs in the profile, only the user who was logged on
when the application was installed will have an entry for
that application on the Programs menu. Other users will
have to create shortcuts to the application on their
Programs menus.

To Dennis:  I checked my documentation thoroughly and it makes no mention of the type of PCI bridge I have, just how to complete the factory install of Windows.  But I gave you the model number of the computer yesterday, let me know if you need more information.

To Smeebud:  I don't have any of the RAM problems you mentioned (lockups, exception errors, etc.), but I'll try the RAM test if nothing else works, and if you still think it's necessary.

To Kent:  I shouldn't have profiles, because when I reinstalled Windows I just put my name in and no password, but I'll check tonight and follow up your and Smeebud's instructions.  And if the profile thing were causing the problem, the icons shouldn't show up when I hit F5, should they?

F5, you're right. No they shouldn't.

Chris99...

You're absolutely right if profife was the problem, F5 should not refresh your desktop, since it does not know who's logged in.

It's a very weird one, I don't think that anyone is on the right track.

Smeebud...
What was your theory behind that profile thing??

Regards

I was following up on kents suggestion.
Until Chriss99 point out the obvious, the f5 refresh.
Now kents answer seems OFF track.

Chris: I Spoke with one of our laisons with Dell, and he suggested a procedure for loading the PCI Bridge, and that should it not work, that you call a number that I will give you directly at Dell as there may be a chip problem. You will need the number(s) off the white tag on the rear of the tower before calling though.

1. Leave the entry for the Pci to Pci Bridge in device manager, which should be listed now as "other devices"

2. Using your Dell disk and the cd, load the PIIX4 drivers on the disk. Reboot.

3. Then reload USB support, then Reboot.

4. Reload the PIIX4 drivers again, and then reboot one final time.

If the problem has cleared up, fine. If not, give them a call at this number:

1-800-624-9896, but you must be at the system when you call. This is a 24/7 number. Tell them you are having trouble installing the Pci to Pci Bridge with your current drivers.

Best regards,
Dennis

Dennis:  The procedure Dell described to you is what I've been doing--exactly what the documentation tells me to do.  And the number he gave is Dell's standard Tech Support line.  The procedure certainly doesn't work, so I'll call them again and mention that a Dell tech thought it might be a chip problem.  I'll post results ASAP.

Thanks,
Chris.

Okay Chris: Mail order tech support being what it normally is, let me know. If nothing else, I'll try and get you the files you need directly from Intel.
Dennis

Chriss,
If this is or is not a problem you and dennis are on, try this anyway:
I've been doing ton's of research on this.
See that you have id your registry your "scrap" option on.
Make sure you have these entries. You can make .reg files out of these as you probably know and click on the to enter the keys and values. BACKUP REG 1ST.
================
REGEDIT4

[HKEY_CLASSES_ROOT\.shs]
@="ShellScrap"
===============
REGEDIT4

[HKEY_CLASSES_ROOT\CLSID\{56117100-C0CD-101B-81E2-00AA004AE837}]
@="Shell Scrap DataHandler"

[HKEY_CLASSES_ROOT\CLSID\{56117100-C0CD-101B-81E2-00AA004AE837}\InProcServer32]
@="shscrap.dll"
"ThreadingModel"="Apartment"
===============
REGEDIT4

[HKEY_CLASSES_ROOT\DocShortcut\DefaultIcon]
@="C:\\WINDOWS\\SYSTEM\\shscrap.dll,-100"
===================
REGEDIT4

[HKEY_CLASSES_ROOT\DocShortcut\shell\open\command]
@="C:\\WINDOWS\\rundll32.exe shscrap.dll,OpenScrap_RunDLL /r /x %1"
====================
REGEDIT4

[HKEY_CLASSES_ROOT\ShellScrap]
@="Scrap object"
"NeverShowExt"=""

[HKEY_CLASSES_ROOT\ShellScrap\shell]
@=""

[HKEY_CLASSES_ROOT\ShellScrap\shell\open]

[HKEY_CLASSES_ROOT\ShellScrap\shell\open\command]
@="C:\\WINDOWS\\rundll32.exe shscrap.dll,OpenScrap_RunDLL %1"

[HKEY_CLASSES_ROOT\ShellScrap\shellex]

[HKEY_CLASSES_ROOT\ShellScrap\shellex\DataHandler]
@="{56117100-C0CD-101B-81E2-00AA004AE837}"

[HKEY_CLASSES_ROOT\ShellScrap\DefaultIcon]
@="C:\\WINDOWS\\SYSTEM\\shscrap.dll,-100"
============================
Before or after this proceedure, try this for me, and you. If you have Word or Wordpad, Highlight about 15 lines or so and drag it to your desktop.
It should appear like this:

      WordPad Document
        Scrap 'THIS IS
           FOR WIN9...'

Just a rhetorical comment, why are computers so difficult to operate?  Those of us who have participated in this discussion are above average computer users at least, and near experts at best.  What can an average user do who simply expects the technology that is blasted at him or her every day, to work?  Why do we tolerate this crap?  It would seem that everything we use in this technology is no more advanced than a well developed alpha.  

Kent
kencam@pobox.com

Now this is an undisputable comment.  And it looks that at the end of our era it will be so complex that the average or above average person will no longer exist on earth.
Just a theory.
Regards

The SOLUTION for this rhetorical question is network computer.
Just *smart* box with cool fast network card and ability co connect
peripherals. Similar to X-Term on Unix. And average and below
average user is prevail on Earth surface, and will.

Chris99,
I didn't see a responce to my suggestion so I'll post it again.
------
Chriss,
If this is or is not a problem you and dennis are on, try this anyway:
I've been doing ton's of research on this.
See that you have id your registry your "scrap" option on.
Make sure you have these entries. You can make .reg files out of these as you probably know
and click on the to enter the keys and values. BACKUP REG 1ST.
================
REGEDIT4

[HKEY_CLASSES_ROOT\.shs]
@="ShellScrap"
===============
REGEDIT4

[HKEY_CLASSES_ROOT\CLSID\{56117100-C0CD-101B-81E2-00AA004AE837}]
@="Shell Scrap DataHandler"

[HKEY_CLASSES_ROOT\CLSID\{56117100-C0CD-101B-81E2-00AA004AE837}\InProcServer32]

@="shscrap.dll"
"ThreadingModel"="Apartment"
===============
REGEDIT4

[HKEY_CLASSES_ROOT\DocShortcut\DefaultIcon]
@="C:\\WINDOWS\\SYSTEM\\shscrap.dll,-100"
===================
REGEDIT4

[HKEY_CLASSES_ROOT\DocShortcut\shell\open\command]
@="C:\\WINDOWS\\rundll32.exe shscrap.dll,OpenScrap_RunDLL /r /x %1"
====================
REGEDIT4

[HKEY_CLASSES_ROOT\ShellScrap]
@="Scrap object"
"NeverShowExt"=""

[HKEY_CLASSES_ROOT\ShellScrap\shell]
@=""

[HKEY_CLASSES_ROOT\ShellScrap\shell\open]

[HKEY_CLASSES_ROOT\ShellScrap\shell\open\command]
@="C:\\WINDOWS\\rundll32.exe shscrap.dll,OpenScrap_RunDLL %1"

[HKEY_CLASSES_ROOT\ShellScrap\shellex]

[HKEY_CLASSES_ROOT\ShellScrap\shellex\DataHandler]
@="{56117100-C0CD-101B-81E2-00AA004AE837}"

[HKEY_CLASSES_ROOT\ShellScrap\DefaultIcon]
@="C:\\WINDOWS\\SYSTEM\\shscrap.dll,-100"
============================
Before or after this proceedure, try this for me, and you. If you have Word or Wordpad,
Highlight about 15 lines or so and drag it to your desktop.
It should appear like this:

WordPad Document
Scrap 'THIS IS
FOR WIN9...'

Bud: We haven't gotten that far yet. At the moment, Chris is trying to resolve a problem getting the correct chipset drivers from Dell. There are two conflicts that are related, the PCI to PCI Bridge and the AGP PCI graphics adapter. When I spoke with Dell, they felt that it could also be either a Bios problem or something wrong with the motherboard itself.
Dennis

What with Thanksgiving and all, I haven't been able to set aside the two hours or so it would take to talk to tech. support, but I will do so as soon as possible.  Smeebud, I did see your suggestion and before I changed anything in the registry, I just opened wordpad and highlighted some lines and dragged them to the desktop, and the scrap thing worked, so I assume it's set correctly.  Should I still look in the registry for the settings you listed?

No need. It works and will save to desktop. Just eliminating possiblities. i've a couple more things to try but will wait as see what happens with what you and Dennis are working on.

You and Dennis have me taking notes on that:))

I just got off the phone with Tech Support.  Since the problem saving to desktop happens in Safe Mode, the tech didn't have any idea of what was causing it.  He did have me change a setting in the BIOS, which didn't fix it, and then he had me unplug the video card and plug it in again.  Which also didn't fix it.  Now he's having a tech come out on Tuesday to install a replacement video card to see if that makes a difference.

I must say, every time I've had to call Dell tech support, they have always been very polite, patient and helpful.  I recommend them, even though my hardware right now is apparently not working at 100%.

Oh--Dennis, about the memory address conflicts between the PCI bridge and the video adapter--the tech said that those conflicts were not a problem.  At first he was going to troubleshoot it, but when I told him the conflict was only in the resources tab and not a yellow exclamation point, he said it was okay.I have heard other people in the Dell newsgroup say they had similar memory address conflicts, and were told that it was not a problem by Dell technical support.  So, although it seems strange to me that a conflict would not be a problem, I guess it's not a problem.  Is it?

Happy Thanksgiving Holiday!  Chris.

Dennis, PCI bridge is not a real root of problem. Note the Chris
said "it happened also in Safe Mode". In Safe Mode works only
Generic VGA driver, compatibility mode HD drivers, no busmaster
stuff at all, no sound. Yikes ! I have an idea. Can this be an
infamous bug of Win95 when user changes "typical machine role"
from Desktop to Network Server ? I don't remember exact registry
locations, but maybe "wise ones" (like smee "registry ace" bud :)
remember. Also maybe need to lower cache size in filesystem.

Chris: Maybe Dell's satisfied with the fact that a memory address conflict is not a problem to them, but a memory conflict of any kind is not acceptable. We've been building systems with the new LX chipset and AGP for several months now, and even at this last Comdex Intel announced that incorrect or  improperly loaded PCI to PCI drivers will cause a problem.
Luke: In response to your comment about the problem happening in safe mode, I presume that to mean that since windows hasn't load the driver, it has nothing to do with the problem. No offense, but you need to spend more time examining motherboard issues. The conflict occurs on an LX motherboard when you move the video card from the standard PCI bus to the AGP (advanced graphics port). In essence, there's no difference in basic structure between a standard PCI video card and an AGP card as to pure function. The difference occurs when the AGP card enables DMA bypassing the CPU, which the standard PCI bus is incapable of. Thus, a memory conflict occurs at boot when the Bios enables the AGP along with the remainder of the PCI bus. When windows boots its drivers and sorts out where everything is supposed to be, it doesn't see the AGP port until the drivers for it load. Normally, the PIIX4 chipset loads first, then the PCI bridge then the AGP along with DMA enable then busmastering is loaded last as part of the board architecture.

Lastly, as for your comment regarding the "Typical Role of this Computer", The setting you use controls the size of various internal data structures used by the 32-bit file access driver (VFAT) that are used to optimize disk space. When you use the Desktop Computer setting, VFAT allocates memory to record the 32 most recently accessed folders and the 677 most recently accessed files. This consumes approximately 10K of memory.
When you use the Mobile Or Docking System setting, VFAT allocates memory to record the 16 most recently accessed folders and the 337 most recently accessed files. This consumes approximately 5K of memory. When you use the Network Server setting, VFAT allocates memory to record the 64 most recently accessed folders and the 2729 most recently accessed
files. This consumes approximately 40K of memory.

At one time, there were issues surrounding making these changes that were supposed to optimize file handling, but they only pertained to the retail version. See MSKB article Q138012.
Even if that were an issue, it would have no bearing on Chris' problem.

Chris, when the tech comes in, tell him about the memory conflict and that the PCI to PCI bridge is not loading and let them fix it properly for you. It may be a Bios or motherboard problem that obtaining an Intel driver will not fix. Oh we know about the issue and it's not a problem is not acceptable. If they need confirmation of that, let me know and I'll give you Intel's engineering phone number.

And Happy Thanksgiving to you too!

We'll be here waiting on you!

Dennis

Well Chriss99,
Here's my 3 year compilation of a good 95 tune-up, and a good registry cleaning. Even if it doesn't fix the save to desktop it's a good thing to do.
-------------
Two Part Windows 95 Tune up.
Many users have complained about Windows95 seizing up for up to
a minute because of random, pointless disk activity. This is due to
the way that Windows95 is set to handle disk caching and virtual
memory.

Although Windows95 instructs you to "let Windows handle disk
cache settings" for best results, this obviously does not yield the best
results. Here's how to eliminate the
1. Random Disk Activity,
2. Improve System Performance
3. Handle Memory More Efficiently
               Part One: Virtual Memory
1. Right click on My Computer, and select Properties.
2. Click the Performance tab, and then click Virtual Memory
3. Choose Let me specify my own virtual memory settings.
4. If you want to choose a different drive for your swapfile, run Disk
Defragmenter first.
5. Specify the same value for the Minimum size and the Maximum
size, so Windows95 won't spend so much time re sizing the file.
A good size is roughly 2 1/2 times the amount of installed RAM (i.e.
create a 40MB swapfile if you have 16MB of RAM).
6. Press OK, and then OK again, and confirm that you want to
restart your computer.
Note: if you have Norton Utilities, you'll be able to optimize the
swapfile. If you want to take the time, you can optimize it manually
by exiting windows, deleting the swapfile, defragmenting the drive,
and restarting. Once you've set the swapfile size to be constant, you
won't have to worry about a defragmented (broken up) swapfile
again.
"The advantage of this process is that Win95 doesn't waste CPU
cycles downsizing the swap file to its auto-set-minimum. Downsize
waste doesn't happen unless enough applications are loaded and
then closed which exceed that minimum. This will be a
low-probability situation if you set the minimum swap file properly."
                Part Two: Virtual Cache
1. Open SYSTEM.INI for editing.
2. Add the following two lines to the [vcache] section (add the
section if it's not there):
-------------------------------
[vcache]
MinFileCache=4096 [Experiment, some people set MinFileCache=0]

MaxFileCache=4096
------------------------------
For 32mg
[vcache]
MinFileCache=8192 [Experiment, some people set MinFileCache=0]

MaxFileCache=8192
------------------------------
3. These values, in kilobytes, regulate the size of the VChache, so
you can stop it from filling up all available RAM and paging all
loaded apps to disk.

Here are several little modifications you can make to improve
Windows95 performance:

Speed up system restart:
1. Add BootDelay=0 to the [Options] section of C:\MSDOS.SYS
Speed up the Start Menu:
2. In the Registry Editor, go to HKEY_CURRENT_USER\ Control
Panel\ desktop, and add a string value named MenuShowDelay, with
a value specifying the number of milliseconds (400 is default, smaller
numbers are faster).
================================

By making a few little tweaks to Windows 95's Control Panel
settings, you can realize some big performance gains. Start by
double-clicking on the Control Panel's System icon, then clicking on
the Performance tab. Next, click on the File System button. You'll
see two settings in the resulting Hard Disk dialog box:
The setting labeled Typical Role of This Machine determines how
much space is set aside in main memory to handle path and filename
caching. The default Desktop Computer choice allocates space for a
paltry 32 paths and 677 filenames, whereas the Network Server
choice bumps those settings up to 64 paths and 2,729 filenames.
Even if your computer is used strictly for desktop applications,
change the Typical Role box to Network Server. Unfortunately, if
you're using the original release of Windows 95--not the recently
updated version titled OEM Service Release 2 (OSR2)--you'll have
to take an additional step to correct a bug in the Windows 95
Registry. Use the Windows 95 Registry Editor (see "Rule the
Windows Registry" for an introduction to the Registry Editor) and
change the value of HKEY_LOCAL_MACHINE\SOFTWARE\
Microsoft\Windows\CurrentVersion\
FSTemplates\Server\NameCache to a9 0a 00 00, and \PathCache to
40 00 00 00.

The Read-Ahead Optimization slider establishes how much
additional data Windows 95 should fetch every time you retrieve
data from your hard disk. Read-ahead buffering improves
performance by reducing the number of times your machine has to
go out to the relatively slow hard disk to get data. Set the slider all
the way to the right, giving Windows 64K of read-ahead buffering.

Next, click on the CD-ROM tab in the File System Properties box.
The Supplemental Cache Size slider adjusts the room Windows 95
sets aside for read-ahead buffering of your CD. The first three steps
on the slider add 64K or 128K each to the cache; the final three
steps add 256K apiece. The box labeled Optimize Access Pattern
For doesn't control access speed to your CD; the setting's real
function is to reserve even more buffer space for caching CD reads.
The Single-Speed Drives and No Read-Ahead settings don't
increase the buffer size.
But the double-, triple-, and quad-speed settings add 50K, 100K, and
150K of cache, respectively.

If you use your CD drive frequently, move the Supplemental Cache
Size slider to Large, and specify that you have a Quad Speed or
Higher CD, even if you don't. The combination will set aside about
1.2MB for CD caching, and ensure that your CD will run as fast as
possible.
---------------
More free memory in DOS windows:

1. Add LocalLoadHigh=1 to the [386Enh] section of SYSTEM.INI.
-
Warning: this may cause unpredictable results if you are not using
the EMM386 memory manager. Remove DoubleSpace/DriveSpace
from memory:
2. Whether or not you're using the DoubleSpace/DriveSpace disk
compression utility, these drivers are taking up valuable memory and
slowing system startup.
3. Simply delete DRVSPACE.BIN and DBLSPACE.BIN from C:\
and your Windows\Command directory. Note: do not do this if you
are currently using DriveSpace or DoubleSpace to compress your
hard disk!! Load DosKey in a DOS box automatically:
4. Right-click on DOSPRMPT.PIF (in your Windows directory),
and select Properties.
5. Click on the Program tab, and enter "DOSKEY" in the field
labeled Batch File. (FYI, I use Keyboost, an antique version of
DOSKEY)
6. Note: for more information, see Contents of the Windows95
MSDOS.SYS File.
Note: some of these settings can also be changed with TweakUI,
one of Microsoft's PowerToys. Warning: several users have
reported problems with this utility - use with caution.
--------------Plus a bonus:))
Get Rid Of Registry Garbage

After a major clean up, you notice that the size of registry remains the same. It's just like how DOS
deletes files on the hard disk. The files are not really deleted, they are just floating.
In the registry a removed key becomes an invisible existence to the reg editors. You can export keys
that are recognizable by the editors to a temp file, then use the same temp file to reconstruct a new
registry. And this is how we remove those invisible footprints.
Clean the bedevil out of your registry. But 1st; BACKUP YOUR REGISTRY.
NOTE: This works on most systems. In my personal experience, and others that I know of it works
75% of the time. If your computer locks up during the process, or does not show 100% done from
"Real Mode Dos", yet stops: Simply reboot and Import MyReg.reg.
Example: C:\Windows>Regedit Myreg.reg
Or, C:\WRP>RESTORE.
-----
WRPV3.ZIP is the Best and easiest Backup/Restore I've Seen. Go To:
http://www.webdev.net/orca/system.html Search WRP
Step1: Copy all .dat files To a Temp directory for Safety.
Step2: Be sure to have a reg backup already.
Step3: Open reg editor and export "all entries" to a reg file(MyReg.reg).
Step4: Shutdown And Boot to DOS. Go to Windows directory.
Step5: Delete .dat files, e.g. del *.dat /y
Step6: If DOS doesn't Recognize the Hidden Files, Type ATTRIB -H -S -R -S SYSTEM.DAT and
ATTRIB -H -S -R -S USER.DAT. Then repeat Step 5. Step7: At C:\Windows> type "regedit /c
MyReg.reg", No Quotes. Done!
NOTE. If this locks your computer up, Simply Import from C:\Windows>Regedit Myreg.reg
That will put everything back the way it was. Everybodys 95 is different, that's why the warning.
Works great for me, not so great for others, so, even if you get the 100%, check you system out,
keyboard, applications, modem; everything! FELL SAFE! You have three backups:
1. MrReg.reg
2. WRP Backup
3. You System.dat and User.dat that you saved in step 1.
After the process, please exam your system thoroughly.
 

Hi everyone!  Are you ready?  Here's the rest of the story.

The problem:
When saving files to desktop, an icon for the file, regardless of file type, will not show up
on the desktop until restart (or click desktop-F5).  Example:  open Notepad.  Type a few
lines.  Click save.  Choose Desktop for Save to.  Click save.  Look on desktop.  
Nothing.  Reboot, and the file appears.  People in Dell newsgroup with similar system
configurations do not have this problem.

The system:
Dell Dimension D266 XPS with single 128-M SDRAM chip, STB Velocity 128 card,
NOT running IE 4.0, 6.4 G HD, OSR 2.1 of Windows 95, purchased in October of this
year.

Attempts to solve:
Arrange icons or line up icons had no effect.  Arrange icons is off.  Various registry tricks
had no effect.  Started in safe mode.  Problem still occurs.  Formatted C: and did a clean
reinstall of Windows 95, installing no hardware or software, with plain VGA drivers.  
Problem still occurs.  Installed Intel update for LX chipset, then USB support, then Intel
update again, exactly as instructed in documentation.  Problem still occurs.  Loaded the
proper Dell-provided STB driver.  Problem still occurs.  Borrowed another copy of
Windows 95 from my wife.  Formatted C:  and did clean reinstall.  Problem still occurs.  
Dell sends technician out to replace video card.  Problem still occurs.  I reformat C: again
and install Windows 95 under the step-by-step guidance of a Dell tech support guy.  
Problem still occurs.

Reason for problem:
The only thing that seems out of the ordinary is in Device Manager, where there is a
memory address conflict between the PCI to PCI bridge and the video driver (regardless
of whether the STB driver or the plain VGA driver is loaded).  Dell, however, says this is
not a problem.  Others say that it can definitely cause problems and there is a finite way to
load the Intel update to fix these problems.  No one has told me yet how to do that.  If
this conflict can be resolved, it MIGHT solve the desktop problem.
If this is not the problem, I guess it could be a bad motherboard or something.  I don't
have a clue.

Why do I care so much about such a minor problem:
1.  I paid $3500 for this system and it should work.
2.  I am having other problems, including problems with Lotus and MS Word, which may
or may not be related to this problem, but the only way I'll be able to rule out the memory
address conflict problem is to fix it.
3.  I paid $3500 for this system and it should work.

Isn't that a great story?  Thanks for your attention.

SMEEBUD:  Although I will certainly follow through your detailed instructions on making Windows 95 generally more fun to be with when the computer seems to be running properly, it's probably not practical right now for me to mess with all the settings when I'm still doing reinstalls every once in a while.  So, unless you think any particular part of all that might help the desktop in particular, I'm going to respectfully reopen the question.

DENNIS:  After talking to tech support, they decided to send a tech out to replace the video card.  The dell tech came out, installed a new video card, no change.  He said he'd never seen anything like it and had no clue how to fix it.  I asked him about the memory address conflict, he said, no, it shouldn't be that way, but didn't know how to fix it.  He called a tech support guy directly and let me talk to him.  The tech support guy asked if I'd mind reinstalling windows.  I said, No, of course not.  He walked me through it, step by step, so there was no chance for an error on my part.  We did, and the problem still happened.  The memory address conflicts were still there, too.  He told me to install the Intel update, USB supplement, and Intel update again, as described in the documentation I have and call him back.  I did and called him back within 15 minutes, got his voice mail, never heard from him again.  This was last night (12-3).  Naturally, I'll continue to try to get through to him, and call tech support again.  

So if YOU have any ideas on how to resolve this conflict, which is apparently NOT A PROBLEM according to Dell, I'm perfectly willing to try them!!!!!!!!  I'll open up the computer and give you serial numbers or whatever!  I just want the thing running CORRECTLY!  And if you have the address of the intel page that reports a problem regarding this memory address conflict, please share!

THANKS IN ADVANCE!!!!
Chris, writing to you from the edge of scenic Insanity!

Chris99,
Wow, what a story. I think it would be a good thing to use my tuneup. It only takes a few minutes and at least we would know your system is running to it's maxixmum. I'd leave out the "Typical Role" change.

How about sending me you system.ini, win.ini, config.sys and autoexec.bat, along with a screen shot of your memory conflict.
Be sure to ZIP them.
smeebud@gte.net.

Also here's a debug bat file to make and run. It will show everything that's getting loaded and more inportantly WHERE
=============
@ECHO OFF
C:\WINDOWS\COMMAND\MEM /DEBUG > TEMPFILE.$$$
C:\WINDOWS\COMMAND\EDIT TEMPFILE.$$$S
DEL TEMPFILE.$$$
==============
This is for my system, you may have to make some path changes.
Copy and save as M.BAT, then run from real dos mode, and after in windows from a dos window.

Don't forget we still have MSD on our CD's.

Check these places for your refreshrate:
----
[HKEY_LOCAL_MACHINE\Config\0001\Display\Settings]
"fonts.fon"="vgasys.fon"
"fixedfon.fon"="vgafix.fon"
"oemfonts.fon"="vgaoem.fon"
"DPILogicalX"="96"
"DPILogicalY"="96"
"DPIPhysicalX"="96"
"DPIPhysicalY"="96"
"MouseTrails"="0"
"BitsPerPixel"="24"
"Resolution"="640,480"
"RefreshRate"="-1"
--------
[HKEY_LOCAL_MACHINE\System\CurrentControlSet\Services\Class\Display\0009\DEFAULT]
"Mode"="8,640,480"
"drv"="mgapdx64.drv"
"vdd"="*vdd,*vflatd"
"minivdd"="mgapdx64.vxd"
"RefreshRate"="-1"
"DDC"="1"
"CHIPID"=hex:00,00,00,00,00,00
------------------------
[HKEY_CURRENT_CONFIG\Display\Settings]
"fonts.fon"="vgasys.fon"
"fixedfon.fon"="vgafix.fon"
"oemfonts.fon"="vgaoem.fon"
"DPILogicalX"="96"
"DPILogicalY"="96"
"DPIPhysicalX"="96"
"DPIPhysicalY"="96"
"MouseTrails"="0"
"BitsPerPixel"="24"
"Resolution"="640,480"
"RefreshRate"="-1"

See that your update mode is 0 not 1
-------
[HKEY_LOCAL_MACHINE\System\CurrentControlSet\control\Update]
"UpdateMode"=dword:00000000

I've been told [have not tried it] that you may create a key called =20 EXAMPLE
[HKEY_LOCAL_MACHINE\System\CurrentControlSet\control\Update\=20]
There you would Add "UpdateMode"=dword:00000000

I hesitate to even comment here among such greatness (no sarcasm intended.. I think all you guys are absolutely brilliant :) but since nobody else has mentioned anything like this... Chris, have you tried using First Aid (or another application like it) to see if it can figure out (and FIX!) what the problem is?

My only other suggestion would be to make DELL reimburse the $3500 (plus some for your time, trouble, headaches) and go out and get a totally different system.

Nnickee...
Thanks for the compliment to all of us, but your idea about FIRST AID is a big NO.  First aid has caused enough problems to people that we have just opted to advise NOT to use it anymore.
Now if you have a different experience with it, cross your fingers.
Regards

Chris: I'd like to be able to offer you a workable or simple solution to this problem, however there appears to be more than a mere software or driver problem here. I suspect that Dell's motherboard has a problem, or at the very least they are having trouble enabling the chipset. After the lengthy diagnosis here, your conversations with the Dell technician, your general experience with the running of the machine and the unresolvable conflict, I suggest that you lean heavily on Dell to replace the machine. It would be easy for me to post an answer to this issue, we work with the LX chipsets every day, and it takes about 45 minutes to load windows and all of the drivers including the AGP card. With that, I suggest that the question remain open until such time as you reach a final determination with Dell. If it will help you, I will email you the chipset driver and updates we use.
Dennis

Dennis:  If you could send me those files, I'd appreciate it.  It may come to Dell replacing the motherboard, but calls to the tech who helped me have so far resulted in voice mail, and calling tech support's main number is on average a thirty minute wait.  It would also be very interesting to be able to inform Dell that this conflict which is "no problem" turns out to be the cause of the problem.  So if you don't mind, I'll at least try it your way and see what happens.

Thanks a LOT!

Chris.

Dennis:  If you could send me those files, I'd appreciate it.  It may come to Dell replacing the motherboard, but calls to the tech who helped me have so far resulted in voice mail, and calling tech support's main number is on average a thirty minute wait.  It would also be very interesting to be able to inform Dell that this conflict which is "no problem" turns out to be the cause of the problem.  So if you don't mind, I'll at least try it your way and see what happens.

Thanks a LOT!  Email:  chrisd@acpub.duke.edu

Chris.

Will do Chris

Try This:
---------
Automatic Screen Refresh
When you make changes to your hard drive and use Explorer, the changes are not usually displayed
until you press the F5 key
To make the updates automatic:
1.Start Regedit
2.Go to HKEY_LOCAL_MACHINE / System / CurrentControlSet / Control / UpdateMode
3.Edit the DWORD value to be between 1 and 7
4.Restart Windows

Dennis, I looked at the readme file for the Intel update you sent me and it didn't mention the 440LX chipset.  It just said 430FX, 430HX, 430TX, 430VX and 440FX.  Is this okay, and the 440LX just didn't get mentioned?

Thanks for sending the files!!
Chris.

Chris: The PCI bridge driver is identical to the 430FX, 430HX, 430TX, 430VX and 440FX. When the inf file is loaded it will load the LX chipset separately. Sorry about that, I should have added a separate text file for you to explain that the PCI driver and LX drivers are different animals. I spoke again with our laison at Intel and he ever so politely informed me that Dell was full of **** as for the conflict not being a problem and need not be resolved.
Dennis

Chriss,
I didn't mean to mark my reg hack answered. Go ahead and reject it as you and Dennis are still working.
Just let me know if it makes any difference.

UPDATE:  Hi.  I've been talking to Dell's customer support all week.  To make a very long story short, they had their engineering department build a computer with the exact components of my system and couldn't duplicate the problem.  Therefore they are sending me a new motherboard and hard drive.  I should get them on Monday or so, so I will post the results.  
They still maintain, however, that the memory address conflict is not a problem, since there is no yellow exclamation point in device manager.  Dennis, I did try to load the software you sent me, but the problem still persisted.  I will try again when the hardware is replaced.  Stay tuned!
Chris.

Okay Chris! I was wondering about you... Don't let up on Dell one inch. Matter of fact, I'll take it a step further if they don't step up and make this right. When the dust settles and should the problem persist, I will arrange a conference call with Dell and you and we'll discuss why there should be no memory conflicts.
Dennis

Chris99

Your updates are very interresting, this makes the case better and worse than it was in the same time.  If Dell team succeeded to duplicate the problem, they will find a solution for it.

As for sending you a new motherboard, that's fine, but I will hold my breath untill it works.  The reason for saying that is:

If Dell succeeded to duplicate the problem, would that point to a unique MOTHERBOARD problem, or all the production line from the same family as your system will reproduce the same problem??

Would reproducing the problem at DELL means that they found another UNIQUE defective motherboard?? or... ????

Anyway, I wish you luck with the new motherboard
Regards

I know what you mean Mag. It sounds like BS to me!

*lol*

FINAL UPDATE

I know you've all been waiting on pins and needles for the result of the last parts replacement attempt.

Long story short:  It WORKED.  The tech came over with a new motherboard and hard drive.  He replaced the motherboard, and was going to replace the hard drive too, but I asked if I could boot the system up and see if the problem still happened.  It did.  So the tech replaced the hard drive.  I asked him if he could wait until I reinstalled Windows to see if the problem was still there (I've done it so many times I can do it in just over ten minutes).  He said okay.  I reinstalled, customized, and restarted sixty or seventy times.  When it was finally done, I tried saving to desktop.  And what to my wondering eyes should appear, but a tiny icon from out of nowhere.  

Well that wasn't particularly short, was it.  A Dell tech called me to follow up (!) the next day.  I called him back and told him the hard drive fixed the problem, although the hard drive passed the diagnostics test.  The tech speculated that it might've been the cache in the hard drive.  I didn't know a hard drive had a cache, but who cares?  It works.

Sorry I haven't written, but I've been installing software left and right (without a hitch, I might add.)  The Lotus problem (with locking up on open) has not yet repeated itself, and I haven't installed Word 97 yet.

Thank you!  Thank you!  Thank you!  Thank you!  Thank you!

I take back all the bad things I first said about this site!  It really is a huge help (even though it didn't seem like it at first).  I recommend it 100%.  

DENNIS:  Thanks, especially, to you.  Of all the experts who helped me, you and Smeebud were the most helpful.  Since I think you were the one who put us and Dell on the right track, I'd like to increase the points to 250 and award them to you.  I don't know if points are even important to you; I don't know exactly how this system works from your standpoint, but if they are, mark this question answered and I will accept the answer.

By the way, the conflict is still there--the memory address conflict between the video card and the PCI to PCI bridge.  I did try to use the drivers you sent me, and the conflict remained.  Dell tells me over and over that the problem is not a problem at all, since there's no yellow exclamation point in Device Manager.  If you think it's worth investigating further, let me know.

Smeebud:  You were a big help too, and although I think Dennis put me on the right track, I'd like to give you 100 points too.  If this is okay with you, I'll ask some lame question like how do you turn the monitor on, and you mark it answered.  Thanks again for your help!  And I definitely will be using all your Windows 95 settings to make everything run smoother.  

And thanks to all the others who made suggestions!

Chriss99,
No need to worry about wasting your points by awarding me some.
I learn on every question. That's enough reward for me. While dennis took care of you PCI bridge issue, I was content to explore and learn about not being able to save to desktop.
BTW, can you do that yet.

Yes!  Yes!  Yes!  Apparently the bad hard drive was causing it, and who knows how many other problems.  I'm glad I wore Dell down and made them realize it was a problem.

But yes, I can save to the wonderful glorious desktop.

And since you won't accept any points, please accept my sincere gratitude.

Thank you!  Thank you!  Thank you!

Merry Christmas!
Chris.

Chris! Wonders abound. I spoke with Jon Anderson at Intel, who tells me that Dell indeed does have a problem with their *proprietary* (made for them in Taiwan) motherboards and the LX chipsets. Apparently Dell's "fits all" motherboards have a design flaw that no one was ware of until after they began trying to resolve the pci bridge issue. Intel is trying to work out a set of drivers to overcome the problem. Dell, as you have indicated, has taken the position that the problem is not a problem. On the otherhand, please keep a close eye on the system, especially regarding performance. If you incur a performance problem, please let me know via email and I will press the issue. In any event, I'm truly glad you have your system up! Merry Christmas to you and yours!
Dennis