![]() | |
![]() |
| | Thread Tools | Display Modes |
#1
| |||
| |||
|
#2
| |||
| |||
|
|
I'm a new DW4 user on a Win98SE system with 256Mbytes of memory and about a Gigabyte of free hard drive space. I realize this is an old product, but it's what I have. |
|
I'm a new DW4 user on a Win98SE system with 256Mbytes of memory and about a Gigabyte of free hard drive space. I realize this is an old product, but it's what I have. DW4 seems to open and work properly, but after perhaps 15-30 minutes, a blank Windows system error dialog box appears, displaying only a CLOSE button (no identification of the error). If I click the button, the application closes, but when I try to open any other application, I get an error message saying "Not enough available memory to run the application" (even if nothing else is running). At that point I have to do Control-Alt-Delete to restart (normal shutdown won't work). It seems that DW4 may have a memory leak. Is this a known problem and if so, how can I fix it? Thanks in advance for your help! Mike |
#3
| |||
| |||
|
#4
| |||
| |||
|
|
I'm a new DW4 user on a Win98SE system with 256Mbytes of memory and about a Gigabyte of free hard drive space. I realize this is an old product, but it's what I have. When you start from a cold boot, what is your System resources value? System Resources is what you see when you do START | Settings > Control Panel > System > Performance Tab And again, what is it after you have been running DW for a few minutes? Running DMX on W9x/Me is going to be something that requires constant intervention to prevent routine OS crashing. The problem is that the operating system is just not able to provide the resources that you are asking it to. Remember that W9x/Me is the last gasp of an OS that was originally developed in 1984. As such either of these are nearly incapable of performing as contemporary environments. All of the W9x/Me variants are based around a memory model that was originally used in W3x. It has changed, but not in a way that would significantly impact this issue since that time. The salient issue in this memory model is the space that is allocated to the OS for scratchpad type work, i.e., tracking what processes are running, what windows are open, what file handles are in use, etc. In 1984, it seemed perfectly reasonable to make this memory segment be 64K (I think that is the right number - could be 48K, though), and it was. However in 2003, that region of memory fills rather quickly. What happens when that scratchpad space fills up? You get General Protection Faults, or Kernel32 errors, or system lockups, or BSOD symptoms. W9x/Me is not graceful when it fails. How can you prevent this from happening? Not by adding more RAM, since that scratchpad size is hardwired in the OS, and since it is taken from the first megabyte of memory, there is not too much you can do by adding hardware. But there is alot you can do in general (although it will not REALLY be enough in the long run). The first thing you have to do is to learn how to monitor this space so you can know where you stand on the "likely to crash" meter - System Resources is what you see when you do START | Settings > Control Panel > System > Performance Tab and a value of less than 30% for this is indicative of a rapidly approaching freight train. Save your files and reboot quickly! After a cold restart, and before running anything else, you *SHOULD* have a SR value of about 80%. If you do not, then you have already added so much to your system (over time, probably) that you can expect to have continuing problems. Look at your System Tray, and see how many icons you have there. Each one of those is a background process that is stealing resources. Do a CTRL-ALT-DEL and look at the processes listed in that Panel. If you have more than about 10, then you are losing lots of your resources to these. The answer is (if you must continue using these antique operating systems instead of upgrading to W2KPro or WXPPro - a much more robust and suitable OS), then you must aggressively prune all of the unnecessary background/startup processes from your system by removing them from your startup process. Using msconfig for this is a good place to start. Hope that helps you - remember 80% after a cold boot will keep you pretty clean. To see more detail on W9x/Me and Resources, go here - http://apptools.com/rants/resources.php ================== -- Murray --- ICQ 71997575 Team Macromedia Volunteer for Dreamweaver (If you *MUST* email me, don't LAUGH when you do so!) ================== http://www.dreamweavermx-templates.com - Template Triage! http://www.projectseven.com/go - DW FAQs, Tutorials & Resources http://www.dwfaq.com - DW FAQs, Tutorials & Resources http://www.macromedia.com/support/search/ - Macromedia (MM) Technotes ================== "Oklahoma Aviator" <webforumsuser (AT) macromedia (DOT) com> wrote in message news:dklmem$2b4$1 (AT) forums (DOT) macromedia.com... I'm a new DW4 user on a Win98SE system with 256Mbytes of memory and about a Gigabyte of free hard drive space. I realize this is an old product, but it's what I have. DW4 seems to open and work properly, but after perhaps 15-30 minutes, a blank Windows system error dialog box appears, displaying only a CLOSE button (no identification of the error). If I click the button, the application closes, but when I try to open any other application, I get an error message saying "Not enough available memory to run the application" (even if nothing else is running). At that point I have to do Control-Alt-Delete to restart (normal shutdown won't work). It seems that DW4 may have a memory leak. Is this a known problem and if so, how can I fix it? Thanks in advance for your help! Mike |
#5
| |||
| |||
|
|
Murray, would Mike's machine handle an upgrade to Win95, and would that afford him some wiggle room on Win housekeeping tasks? "Murray *TMM*" <forums (AT) HAHAgreat-web-sights (DOT) com> wrote in message news:dklqup$7it$1 (AT) forums (DOT) macromedia.com... I'm a new DW4 user on a Win98SE system with 256Mbytes of memory and about a Gigabyte of free hard drive space. I realize this is an old product, but it's what I have. When you start from a cold boot, what is your System resources value? System Resources is what you see when you do START | Settings > Control Panel > System > Performance Tab And again, what is it after you have been running DW for a few minutes? Running DMX on W9x/Me is going to be something that requires constant intervention to prevent routine OS crashing. The problem is that the operating system is just not able to provide the resources that you are asking it to. Remember that W9x/Me is the last gasp of an OS that was originally developed in 1984. As such either of these are nearly incapable of performing as contemporary environments. All of the W9x/Me variants are based around a memory model that was originally used in W3x. It has changed, but not in a way that would significantly impact this issue since that time. The salient issue in this memory model is the space that is allocated to the OS for scratchpad type work, i.e., tracking what processes are running, what windows are open, what file handles are in use, etc. In 1984, it seemed perfectly reasonable to make this memory segment be 64K (I think that is the right number - could be 48K, though), and it was. However in 2003, that region of memory fills rather quickly. What happens when that scratchpad space fills up? You get General Protection Faults, or Kernel32 errors, or system lockups, or BSOD symptoms. W9x/Me is not graceful when it fails. How can you prevent this from happening? Not by adding more RAM, since that scratchpad size is hardwired in the OS, and since it is taken from the first megabyte of memory, there is not too much you can do by adding hardware. But there is alot you can do in general (although it will not REALLY be enough in the long run). The first thing you have to do is to learn how to monitor this space so you can know where you stand on the "likely to crash" meter - System Resources is what you see when you do START | Settings > Control Panel > System > Performance Tab and a value of less than 30% for this is indicative of a rapidly approaching freight train. Save your files and reboot quickly! After a cold restart, and before running anything else, you *SHOULD* have a SR value of about 80%. If you do not, then you have already added so much to your system (over time, probably) that you can expect to have continuing problems. Look at your System Tray, and see how many icons you have there. Each one of those is a background process that is stealing resources. Do a CTRL-ALT-DEL and look at the processes listed in that Panel. If you have more than about 10, then you are losing lots of your resources to these. The answer is (if you must continue using these antique operating systems instead of upgrading to W2KPro or WXPPro - a much more robust and suitable OS), then you must aggressively prune all of the unnecessary background/startup processes from your system by removing them from your startup process. Using msconfig for this is a good place to start. Hope that helps you - remember 80% after a cold boot will keep you pretty clean. To see more detail on W9x/Me and Resources, go here - http://apptools.com/rants/resources.php ================== -- Murray --- ICQ 71997575 Team Macromedia Volunteer for Dreamweaver (If you *MUST* email me, don't LAUGH when you do so!) ================== http://www.dreamweavermx-templates.com - Template Triage! http://www.projectseven.com/go - DW FAQs, Tutorials & Resources http://www.dwfaq.com - DW FAQs, Tutorials & Resources http://www.macromedia.com/support/search/ - Macromedia (MM) Technotes ================== "Oklahoma Aviator" <webforumsuser (AT) macromedia (DOT) com> wrote in message news:dklmem$2b4$1 (AT) forums (DOT) macromedia.com... I'm a new DW4 user on a Win98SE system with 256Mbytes of memory and about a Gigabyte of free hard drive space. I realize this is an old product, but it's what I have. DW4 seems to open and work properly, but after perhaps 15-30 minutes, a blank Windows system error dialog box appears, displaying only a CLOSE button (no identification of the error). If I click the button, the application closes, but when I try to open any other application, I get an error message saying "Not enough available memory to run the application" (even if nothing else is running). At that point I have to do Control-Alt-Delete to restart (normal shutdown won't work). It seems that DW4 may have a memory leak. Is this a known problem and if so, how can I fix it? Thanks in advance for your help! Mike |
#6
| ||||
| ||||
|
|
When I received your post, I checked system resources and found them to be running about 38% |
|
I don't have many background processes running |
|
One last question: with a modern OS, is DW4 still supported and, if so, where would I find support info for it? |
|
Thanks very much, Murray--sounds like a cogent explanation you provided! Of course, it's not what I want to hear--it means I'll probably wind up buying a new computer, since my processor speed probably won't handle the new operating systems. When I received your post, I checked system resources and found them to be running about 38% (I had been running DW4 for about a half hour at that point). I rebooted and found they were running at 73%. I don't have many background processes running, but I'll see what I can do to remove as many as possible. One last question: with a modern OS, is DW4 still supported and, if so, where would I find support info for it? Thanks! Mike |
![]() |
| Thread Tools | |
| Display Modes | |
| |