Memory could not be "Read" problem

[Snorre]

This warning message seems to be a rather common problem but little if any information can be found to help solve the problem. In my case, most of the time it just causes the current operation to terminate, and I can the start it again without any problem.

The whole message reads something like "Instruction at address 0x........ points at address 0x........... Memory could not be "Read".

The OS is Win2kSp4 that has been working flawlessly for something like ten years before the messages began popping up. I wouldn't mind so much except in certain situations when running the Visual Foxpro Debugger, making it impossible to continue. Repeating the operation is useless.

BTW, the memory is sometimes referred to as 'cold not be "Written".

I believe the problem is within the Windows system, and have a possible remedy in mind: To replace as much, i.e. files in the WINNT folder that can be replaced without disrupting the system. Which files should I not touch? I know the registry is crucial, but what is/are the file name(s) to look out for?

I have a complete backup of the boot drive. I have tested restore and that works fine.

And oh yes, I can of course reinstall Windows, but will I be able to rebuild my setup? I have divided the installation into three disk partitions: system C:\ , programs D:\Prog\, and data E:\ (Plus a small F:\temp) and see that as a great problem; I remember editing some fields of the registry in order to make that work.

Would installing Windows for scratch to just one large volume, C:, copying programs to C:\Program Files, and the data to ? be a better approach?

I have several reasons for still using Win2k: It is reliable, it works, and I am familiar with it. It is also the only OS that AFAIK will run MusicMatch. Besides, at 80, I'd rather not be bothered with becoming comfortable wit a new and probably 'better system like Win7.

Sorry for a long 1st. post...

[-pops-]

This error used to be quite common but, since MS moved over to the NT system, it doesn't occur any longer (or only very rarely).

You state that your reasons for using W2K are that it is reliable and it works. Well, your post indicates neither of those statements are true.

Unfortunately, MS no longer supports W2K. It would be far better for you to move over to a more modern version (W7) - you say you are prepared to re-install and such, why not go the whole way and update as well.

There are a number of us who are of a similar vintage to yourself and I think that most, if not all, would agree that an up-to-date computer tends to keep your brain up-to-date as well. I certainly find that, I just wish I was nimble enough now to be able to construct computers as I used to.

This article from MS gives some info. http://support.microsoft.com/kb/262490

[Boris]

I used to use MUSICMATCH Jukebox - before Yahoo took them over ............. and it runs OK on XP.

Versions of MUSICMATCH Jukebox that are earlier than version 7.1 are not completely compatible with Windows XP.

Later ones shuld be fine.

You can download the last MusicMatch version before they were taken over (MusicMatch Jukebox 10.00.4033) from here :-
/>http://www.oldversion.com/MusicMatch_Jukebox.html

[ɹəuəllıʍ ʇɐb]

Is that error message something that has suddenly started, and does it happen with different programs?

Usually this message indicates that something is wrong with a certain program, but it could also be the case that something is wrong with your memory (RAM).

Use a memory test program to find out if your RAM needs replacement. I cannot recommend any specific program, but Google will help you to find one.

[Snorre]

Thanks for replies. A decade of flawless (except maybe a very few minor wrinkles) operation tells me it it reliable, and it really was, until this problem appeared.

Main reason for not using Win7 is the MusicMatch incompatibility. I usually work with the jukebox running while I'm using the system. Plus, it seems to me that the screens and windows look different from what I am used to? (IIRC, most noticeable in VFP programs) Even the colors were different. But to be fair, I'll give Win7 another try, I have it installed on a separate drive with all my programs and data installed an emergency measure. Plus backup of everything on external storage.

since MS moved over to the NT system

But isn't Win2k a NT system? IIRC, it even advertise itself as NT Technology.

I am not about to give up quite yet but may have too, have wasted too much time on it already.

First thing I'd like to try is to have two instances of Win2k on the same drive\partition for some experiments but I don't know if that's possible. Can't use the Windows installer, gives trouble on drives over 128GB. Can work work around that, but don't know how to, if possible to configure.

[-pops-]

OK, a small error on my part about the pedigree of W2K but, the remainder of my post is relevant.

W2K is an obsolete system and machines that use it are similarly classified. You state you "have wasted too much time on it already." I can only surmise that you will continue to do that in pursuing this project.

Do give W7 another try - I'm sure that when you get familiar with its extra facilities that it will do much more than the system you're used to. In regard to you music program, I would expect there are similar (and improved) ones available for W7.

[Snorre]

You are of course quite right and is about time I did something about it. And I will!

[ɹəuəllıʍ ʇɐb]

First of all, I'd like you to know that I am writing this on my faithful Win2K system. Yes, the machine is old, and some day it will need replacement, but for now it's doing its job very nicely!

First thing I'd like to try is to have two instances of Win2k on the same drive\partition for some experiments but I don't know if that's possible. Can't use the Windows installer, gives trouble on drives over 128GB. Can work work around that, but don't know how to, if possible to configure.

You can partition your HD into two, and install another instance of Windows in the 2nd partition. The Windows Boot Manager will give you a choice at boot time what system to start.

If you need help setting this up, let us know - any of us use a multi-boot system.