I've been having trouble running  "learn visual basic" software and someone suggested that I might have a "leak in my registry."  Anybody know what that is?

My thanks,

Debbie

I apologize for not being more clear in my last post.  I have Windows 98. The information I received for the "Registry Quota Leak" was for 2000.  Any hints for 98?

Again my thanks.

Debbie

Are you sure they said "A leak in the registry" and not"A leak in the disk cache"?

Wow, thanks for the quick reply!  I guess I'm not sure how to tell if that's the problem or not....(can you tell I'm a beginner?)  We haven't had the problem with any other programs, just attempting to use a "Learn to Program" book/cd.  It works on other computers, just not ours.  I know when I take it in to Best Buy, they'll simply reinstall Windows.  Having done that, I know it's not the problem.

Hi Debbie,

Just to expand on what Sandra said, we need a little more information. Perhaps you could clarify the following:

1.  Have you actually managed to install Learn Visual Basic?  If not, how far do you get and what error messages are you getting, if any, or what actually happens?

2.  If you have sucessfully installed LVB, does the program actually run?  Any error messages?  If it runs, at what stage are your problems occurring, and what actually happens?  Error messages, again, can be a help with diagnosing problems, so if you could note exactly what any messages say, and let us know, hopefully someone will be able to help you.

It probably won't be me though - I'm just saving the experts the job of asking the questions!  

You folks are so fast!  I'm very impressed.  I'm working from a very beginning book called Teach Yourself Visual Basic 6 in 24 hours.  It installs well   (that much I can do).  When you try to run the simplest program, however, it just says "VB6 caused an illegal page fault in module VB6.exe at 0167:60475lfl."  In other programs I occasionally get a message that says "a dll file is missing."  Any connection?

I will definitely do the registry checker thing.  Thanks, again.

Debbie

Hopefully this may be the solution Debbie.
It may look daunting to you at first but re read it and follow the instructions step by step and it should be ok.
It may be easier if you print the page off so you can have it at hand while you follow the instructions,I would copy and paste it into notepad and refer to it there but some people prefer it on hard copy  

http://support.microsoft.com/default.aspx?scid=kb;en-us;249879

Edited as I forgot to put the link in again  

No problem Debbie - the trouble with us techies is that we all speak a different language from English

You have to type in the address of the file on your computer (the path) instead of the  <x>:\<path> bit. An easy way to find out where the  Ssscc.dll file might be is to use the Find files and folders facility on the Start menu.

If you cannot find this file, then I would think that Sandra's solution isn't going to work for you

ARggh, I don't want to worry you debbie, after all I'm just a new guy around here too, and haven't got my status up   but invalid page faults are not too healthy.

Again, if I remember correctly: your hard disk will use a little space to pretend to be memory. When your memory fills up and needs more space it will swap older data out to the hard disk, and replace it with new stuff. If the old stuff is required, then its still on the HDD ready to be retrived, albeit a little slower.

Now, data in memory or HDD is referenced by pointers. When you want something the pointer says "ITS HERE ---->", but what happens if its not there? Data is 1's and 0's - if that data has been changed from 1 to 0, then that's bad.

just FYI, radiation from the sun will change a 1 to a 0 about once a month in a memory module, and will usually crash your machine because of it! Server use special memory to try and combat this as well as other problems... anyway - off track here...

its possible that (worst case) you have a memory problem, which I don't think because you would have a restarting machine more often. I think its better to say there may be a POINTER issue with your harddisk. If you really can't get it sorted by any normal easy way, do the drastic thing and reinstall Windows so that it purrrrs (if windows ever actually did/does).