Error - template LAYOUT-DATA-WRAPPER not found

A configuration error was detected in the CGI script; the LAYOUT-DATA-WRAPPER template could not be found.

Error - template STYLE-SHEET not found

A configuration error was detected in the CGI script; the STYLE-SHEET template could not be found.

Error - template SUB-TOP-BANNER not found

A configuration error was detected in the CGI script; the SUB-TOP-BANNER template could not be found.
Subject:
From:
David Gillett <[log in to unmask]>
Reply To:
PCSOFT - Personal Computer software discussion list <[log in to unmask]>
Date:
Mon, 24 Aug 1998 13:07:47 -0800
Content-Type:
text/plain
Parts/Attachments:
text/plain (61 lines)
On 22 Aug 98 at 23:31, Paul R Sprague wrote:

> I have a very persistent problem with Windows 95 OSR2 and I would
> appreciate some help in resolving it. Every time I exit control panel it
> goes to a blue screen stating the following message:
>
> "Fatal Exception 0E has occurred at 0028:C0286E19 in VXD IFSMGR(4) +
> 0000D4F1
> The current application will be terminated."

  IFSMGR is the "Installable File System ManaGeR", the module that
provides 32-bit code for file operations.  Looks like a file system
or hard drive issue....

> After this occurs, I hit "Enter" and Windows is back up and running
> as if nothing happened. The only thing I notice is that all the
> System Tray icons are gone.

  Explorer will restart itself if it gets terminated, but it doesn't
restart tray items (which may still be running, only the new instance
of Explorer doesn't know about them...).

> I have tried everything I can possibly think of to correct the
> problem. I have removed all items from the start-up folder. I have
> shut down all TSR's using CTRL + ALT + DEL  and clicking End Task
> for each item except Explorer which as you know will shut down
> Windows.

  See my remark above; I think the behaviour when Explorer is
terminated may have changed in OSR2.

> I have manually specified vertual memory settings at a minimum and
> maximum of 192 MB which is 3 times my RAM. I have put the filing
> system settings at "Network Server". I also did a file search on
> "IFSMGR.VXD" and found that it is stored in the
> C:\Windows\System\Vmm32 Directory if that is any help to anyone. If
> I am not mistaken, I believe that VMM stands for Virtual Memory
> Manager thus the reason I played with the virtual memory settings.

  Virtual Machine Manager, actually.  .VXDs are virtual device
drivers, and they run in the "virtual machine" context.
  If you were letting Windows manage your virtual memory, I'd guess
that the crash might be happening when Windows tries to shrink the
swap file.  But that can't be the case.
  Do you have bus-mastering drivers installed for your EIDE
controller?  [Check Device Manager for drive controller drivers....]

> These are my system specs:
>
> Octek Rhino 15 Socket 7 motherboard 430TX Chipset
> 64MB SDRAM
> AMD K6 233mhz MMX Processor
> Western Digital 2.5GB Hard Drive
> Creative Labs AWE 64 Value Sound Card
> US Robotics 33.6 Winmodem
> HP Scanjet 6100C SCSI Scanner
> Parallel Port Zip Drive
> 12X IDE CD ROM

David G

ATOM RSS1 RSS2

LISTSERV.ICORS.ORG Secured by F-Secure Anti-Virus CataList Email List Search Powered by LISTSERV