When I start up PI10 and go to file--->open, as I search for the drive and folder that I want, the program will suddenly freeze. Task manager reports it as "Not Responding" so I "end task". When I restart PI10 and do the exact same thing (file--->open, etc), it works fine and all is well.
It's annoying to have to do that every time and I can't figure out what is wrong. Otherwise, I really like PI over PSP9. Can anyone help?
Computer specs:
P4 2.4GHz
1G RAM
256MB AGP ATI Radeon x800GTO
12G HD space
WinXP Home
2G min/max virtual mem.
PI10 Requires Two Start-Ups
-
heinz-oz
I don't think there is anyone else out there with your particular problem, at least we haven't heared of one here. Having said that, no, that behaviour is not normal but I also don't believe that it is PI that's causing this.
Have you checked your RAM memory used on your system?
Please also check this thread http://phpbb.ulead.com.tw/EN/viewtopic. ... hlight=ram
The 8th or so post down gives the url's for some free downloads of memory checking programs.
Have you checked your RAM memory used on your system?
Please also check this thread http://phpbb.ulead.com.tw/EN/viewtopic. ... hlight=ram
The 8th or so post down gives the url's for some free downloads of memory checking programs.
-
keenart
2 gig min\max virtual memory? Did you try letting Windows manage Memory?
Right click on MY Computer and Select Manage. On the computer Management dialog box select Device Manager and expand the tree. Look and see if there are any yellow exclamation marks to indicate a faulty device.
Also click on the Event Viewer, and look through all three trees, Applications, Security, and System and see if there is an Error or Warning about an application. If there is right click on the application, select properties and find out what the problem is.
If none of the above try turning off, in Ulead's Preferences, the Browse Manager Cache.
Right click on MY Computer and Select Manage. On the computer Management dialog box select Device Manager and expand the tree. Look and see if there are any yellow exclamation marks to indicate a faulty device.
Also click on the Event Viewer, and look through all three trees, Applications, Security, and System and see if there is an Error or Warning about an application. If there is right click on the application, select properties and find out what the problem is.
If none of the above try turning off, in Ulead's Preferences, the Browse Manager Cache.
-
Fotogrfr
Thanks for the replies, keenart and heinz-oz.
I've tried a number of things you've both suggested
... Turned off Browse Manager Cache
... Let Windows control my Virtual Memory
... Moved my Virtual Memory to the same harddrive PI10 is on
Nothing has eliminated my problem.
I know my RAM is good. I do have a little glitch showing up in Device Manager since installing a new video card but this problem was happening before I made that change so I don't think it has anything to do with that.
For the most part, it seems that if I fire up PI10 right after booting, it works. However, if I do anything else on the computer and THEN fire up PI10, I get the freeze and have to "end task" and restart PI10. After doing that, then it works fine.
How the heck much RAM does this program want?
I've tried a number of things you've both suggested
... Turned off Browse Manager Cache
... Let Windows control my Virtual Memory
... Moved my Virtual Memory to the same harddrive PI10 is on
Nothing has eliminated my problem.
I know my RAM is good. I do have a little glitch showing up in Device Manager since installing a new video card but this problem was happening before I made that change so I don't think it has anything to do with that.
For the most part, it seems that if I fire up PI10 right after booting, it works. However, if I do anything else on the computer and THEN fire up PI10, I get the freeze and have to "end task" and restart PI10. After doing that, then it works fine.
How the heck much RAM does this program want?
-
heinz-oz
I Gb RAM should be enough. Do I read your first post right, you have 12 GB free space?
Having Windows control the virtual memory will fragment your free space on your disk very quickly. I have used identical min/max settings of 2.5 x physical RAM for years. You do need to keep a small amount of virtual memory on your system disk though to allow the system to create a memory dump in case of a fatal error. I have that set to 172MB min/max.
I think your system is running out of virtual memory space on the HDD.
Having Windows control the virtual memory will fragment your free space on your disk very quickly. I have used identical min/max settings of 2.5 x physical RAM for years. You do need to keep a small amount of virtual memory on your system disk though to allow the system to create a memory dump in case of a fatal error. I have that set to 172MB min/max.
I think your system is running out of virtual memory space on the HDD.
-
Fotogrfr
Yes, I agree about the fragmentation with Win controlling virtual memory. That's one reason I had it set min/max at 2G to start with. Anyway, I've re-set it to that, however, it sounds like you think it should be even more.heinz-oz wrote:I Gb RAM should be enough. Do I read your first post right, you have 12 GB free space?
Having Windows control the virtual memory will fragment your free space on your disk very quickly. I have used identical min/max settings of 2.5 x physical RAM for years. You do need to keep a small amount of virtual memory on your system disk though to allow the system to create a memory dump in case of a fatal error. I have that set to 172MB min/max.
I think your system is running out of virtual memory space on the HDD.
I would have to clear some things from my harddrive to get more than 12G of free space. I will work on that.
What would you suggest for the following...
Amount of free harddrive space?
Amount to set virtual memory min/max?
I could just try experimenting, but if you have some suggestions for starter points, I would greatly appreciate it.
Thanks again. You've been very helpful... not to mention patient.
I really like PI10 and hope to get this sorted out. Then maybe I'll upgrade and have a whole new set of problems! Naaa, I think I'll wait for PI12.-
keenart
Microsoft's suggestion, let Microsoft Manage the Virtual Memory and it will automatically set the parameters needed in relation to the size of the drive. It will reamain at a minimum size until needed and then grow to the required size when the demand arises.
Again, MS suggests you have at least 25 percent of your hard drive open. It may be cheaper to install a second hard drive.
If you can use the NTFS file system, it takes less drive space and is more stable that Fat32x.
I would ask, what type of Firewall are you using as this can sometimes stop PI in its tracks.
Again, MS suggests you have at least 25 percent of your hard drive open. It may be cheaper to install a second hard drive.
If you can use the NTFS file system, it takes less drive space and is more stable that Fat32x.
I would ask, what type of Firewall are you using as this can sometimes stop PI in its tracks.
-
Fotogrfr
There's a second harddrive in there already (FAT32). It has less space than the main harddrive (which is NTFS). Between my photos, one or two space-hungry games, and the files resulting from capturing/editing my VHS tapes for burning onto DVD, space fills up fast. However, I also have a couple of USB drives attached so I will move stuff around and clear things out.keenart wrote:Microsoft's suggestion, let Microsoft Manage the Virtual Memory and it will automatically set the parameters needed in relation to the size of the drive. It will reamain at a minimum size until needed and then grow to the required size when the demand arises.
Again, MS suggests you have at least 25 percent of your hard drive open. It may be cheaper to install a second hard drive.
If you can use the NTFS file system, it takes less drive space and is more stable that Fat32x.
I would ask, what type of Firewall are you using as this can sometimes stop PI in its tracks.
That particular computer is not hooked up to the internet at all... it's only used for those aforementioned purposes so no firewall is running.
I'll keep you posted.
-
heinz-oz
I don't know why MD recommends to follow Microsoft's recommended procedure, that's for him to live with. I have, for a number of years now, set my virtual memory to 172 MB min/max on the system drive and another 2.5 times the physical RAM on a separate physical drive. The min/max settings are identical there too.
As MD describes, WIN is going to run with a smaller virtual memory filetil it needs more space. That space will not be available right next to the current file (non-contiguous file used) and will be allocated anywhere on the disk. When it is no longer needed, the file will shrink again, possibly not as small as it was before and the previously used space will be available again to WIN to use for something else. Even this small example of WIN behaviour should demonstrate why the swap file is the biggest contributor to HDD fragmentation.
Of course, that is only part of your problem. When you open an image in PI, a multiple of the original file size is required by PI to work on that image. PI will create temp files while you are working, keeping track of all the manipulations of your image undertaken. This can be a hefty filesize, depending on the level of Undo's you have enabled.
I just felt that 12 GB is rather smallish, especially when there are other things taking up temp space in the background or if the available space is not contiguous. WIN will only allocate complete blocks for storage but, AFAIK, partially free segments of allocated blocks are still shown as free space. Hence, the available free space, in full blocks, can be considerably less than what WIN reports as free.
I don't have a recommendation as to minimum free space, I just prefer to have ample.
As MD describes, WIN is going to run with a smaller virtual memory filetil it needs more space. That space will not be available right next to the current file (non-contiguous file used) and will be allocated anywhere on the disk. When it is no longer needed, the file will shrink again, possibly not as small as it was before and the previously used space will be available again to WIN to use for something else. Even this small example of WIN behaviour should demonstrate why the swap file is the biggest contributor to HDD fragmentation.
Of course, that is only part of your problem. When you open an image in PI, a multiple of the original file size is required by PI to work on that image. PI will create temp files while you are working, keeping track of all the manipulations of your image undertaken. This can be a hefty filesize, depending on the level of Undo's you have enabled.
I just felt that 12 GB is rather smallish, especially when there are other things taking up temp space in the background or if the available space is not contiguous. WIN will only allocate complete blocks for storage but, AFAIK, partially free segments of allocated blocks are still shown as free space. Hence, the available free space, in full blocks, can be considerably less than what WIN reports as free.
I don't have a recommendation as to minimum free space, I just prefer to have ample.
-
keenart
Once you have cleaned your drives out and made a little space you might consider cleaning out your temp folders and then defragging the drive about three times. If you are working with large files then you will probably have a lot of degfragmentation which can cause strange behavior when trying to launch an application.