Mounted DVD causes memory problems

[phöènix]

I had a problem with explorer.exe loading over 350MB into memory and
swapping in and out of VM virtually locking the system.

I tracked the problem down to a DVD as an ".img" file mounted using
Alcohol1120. While the image file was mounted any use of windows (eplorer
below a couple of levels) would trigger the memory usage.

I discovered that if the same file is renamed to ".iso" then mounted the
problem does not recurr.

I have not seen any other references to this problem and was wondering if
anyone had any comments. Is it likely that the way my system is configured
to treat .img is causing this. If so what settings/ keys are likely
suspects.

".img" is not a registered file type on my system.

 

[Malke]

I had a problem with explorer.exe loading over 350MB into memory and
swapping in and out of VM virtually locking the system.

I tracked the problem down to a DVD as an ".img" file mounted using
Alcohol1120. While the image file was mounted any use of windows
(eplorer below a couple of levels) would trigger the memory usage.

I discovered that if the same file is renamed to ".iso" then mounted
the problem does not recurr.

I have not seen any other references to this problem and was wondering
if anyone had any comments. Is it likely that the way my system is
configured to treat .img is causing this. If so what settings/ keys
are likely suspects.

".img" is not a registered file type on my system.

Alcohol 120% is a program that allows you to mount virtual drives, among
other things. Here is its home page:

http://www.alcohol-software.com/

Using virtual drives does consume a fair amount of memory, and you
didn't tell us how much you have or what else you're trying to run. I
think the best place for you to find information on your error is from
Alcohol's tech support.

Good luck,

Malke

 

[phöènix]

I had a problem with explorer.exe loading over 350MB into memory and
swapping in and out of VM virtually locking the system.

I tracked the problem down to a DVD as an ".img" file mounted using
Alcohol1120. While the image file was mounted any use of windows
(eplorer below a couple of levels) would trigger the memory usage.

I discovered that if the same file is renamed to ".iso" then mounted
the problem does not recurr.

I have not seen any other references to this problem and was
wondering if anyone had any comments. Is it likely that the way my
system is configured to treat .img is causing this. If so what
settings/ keys are likely suspects.

".img" is not a registered file type on my system.

[snip]

Using virtual drives does consume a fair amount of memory,

Fair amount?

Never 350MB IME nor as I said have I seen anyone else mention anything
similar.

and you
didn't tell us how much you have or what else you're trying to run.

I don't think how much I have is particularly relevant. Explorer.exe is
using around 350MB more than when the same DVD is renamed and mounted as an
ISO.

The only thing I am trying to run is use explorer.exe.


The problem is reproducable in Safe Mode and diagnostic mode with minimum
processes running.

I
think the best place for you to find information on your error is from
Alcohol's tech support.

You're probably right, which is why I looked ther first but covering the all
the bases seems a good idea when dealing with an apparently rare problem and
MS SW.

 

[Alex Nichol]

I tracked the problem down to a DVD as an ".img" file mounted using
Alcohol1120. While the image file was mounted any use of windows (eplorer
below a couple of levels) would trigger the memory usage.

I discovered that if the same file is renamed to ".iso" then mounted the
problem does not recurr.

I have not seen any other references to this problem and was wondering if
anyone had any comments. Is it likely that the way my system is configured
to treat .img is causing this. If so what settings/ keys are likely
suspects.

This sounds like something to blame on the Alcohol1120 - it is doing the
work on an .img, and is doing it by loading the entire image into
Virtual memory in one unit (or maybe in multiple but still enormous
units). which is not likely to be a productive approach.