SIMpe Issues

[liegenschonheit]

Okay, this should probably be posted at the SIMpe forum, but since I don't go there I thought I would ask here first before making a whole new account to ask a question. Ahem.

When exiting SIMpe, has anyone else noticed that you have to manually kill the process or it closes out the program but the process stays alive and sucks up all your memory? Or is it just me and I have a broken version of SIMpe?

[jrd]

No, that's fairly common for all .Net 1 programs. I used to get it all the time.

The new SimPE will run on .Net 2 and this issue has been mostly stomped.

[jsalemi]

Not only that, but it keeps any files you've modified locked until you reboot the system.  I use MSs SyncToy to keep my downloads folder synced between my desktop and laptop, and it can't copy over files that I've recently modified in SimPE until I reboot the desktop.

[Hegelian]

When exiting SIMpe, has anyone else noticed that you have to manually kill the process or it closes out the program but the process stays alive and sucks up all your memory? Or is it just me and I have a broken version of SIMpe?

FWIW, I haven't experienced this myself. I do have .NET 2 installed.

Not only that, but it keeps any files you've modified locked until you reboot the system.  I use MSs SyncToy to keep my downloads folder synced between my desktop and laptop, and it can't copy over files that I've recently modified in SimPE until I reboot the desktop.

I don't seem to have this problem. Just this afternoon I modified three files in a location outside the Downloads folder and then moved them to their apppropriate subfolder with no problems. OTOH, Windows occasionally won't release a file or folder even though no app is using it (apparently), requiring a reboot. I suspect the apparent relationship between SimPE and Windows not releasing files is a case of false causation:  cum hoc ergo propter hoc ("with this, therefore because of this").   

[Jelenedra]

I had that issue with one of my Baldur's Gate protraits. It wouldn't let me delete the folder until after I rebooted the pc. Which was weird, because all of the other folders I deleted gave me no problem....

[liegenschonheit]

I just started having this problem and it is sucky. However, I also have .net 2 installed, so I will grab that version of SIMpe and see if it solves my issues.

Thanks Jordi.

Also guys, for me, it usually unlocks the files after I manually terminate the process. I usually don't have to reboot.

[jrd]

A way to get around locked files is to kill the explorer.exe process, remove or rename the file or folder using a commandline ("DOS prompt"), and restart the explorer.

[jsalemi]

Not only that, but it keeps any files you've modified locked until you reboot the system.  I use MSs SyncToy to keep my downloads folder synced between my desktop and laptop, and it can't copy over files that I've recently modified in SimPE until I reboot the desktop.

I don't seem to have this problem. Just this afternoon I modified three files in a location outside the Downloads folder and then moved them to their apppropriate subfolder with no problems. OTOH, Windows occasionally won't release a file or folder even though no app is using it (apparently), requiring a reboot. I suspect the apparent relationship between SimPE and Windows not releasing files is a case of false causation:  cum hoc ergo propter hoc ("with this, therefore because of this").   

It's not a problem moving the files around on the same machine -- it only crops up when I try to copy them from one machine to another.  I get all kinds of 'can't access' messages, usually the one saying the file is in use by another process.

[SaraMK]

A way to get around locked files is to kill the explorer.exe process, remove or rename the file or folder using a commandline ("DOS prompt"), and restart the explorer.

Most times you can kill explorer, restart explorer, and the files/folders are unlocked. I'm clueless about DOS so this is how I do it, and it works most of the time. For me, SimPE is horrible about locking up empty folders for some reason.