Post by xxgeek on Jul 6, 2021 18:12:03 GMT
Something I should mention for more clarity --
Once an exe file is created, and you click to open it, it unpacks all the sll;dll and other needed files to a temp dir (beyond my control) I can't be sure where it puts these temp files on everyones PC. I assume they go to the environment variable for temp files, but found out this may not be the case. On my machine I have my temp variables set to go to my ramdrive, but the temp files created when one of these exe files is executed are going to a temp folder on my D; drive, not my C: drive, or my ramdrive, and at this time I haven't figured out why.
When the exe file is executed it unpacks to the dir D:\msdownld.tmp and creates a new folder for every exe file executed, and saves them even after a reboot. So, not so temporary. If you execute the same exe file, it creates a new dir instead of using the one already there, so these folders can add up over time (full of dll, sll and the other files for runtime.)
The folders created in D:\msdownld.tmp are named IXP000.tmp, IXP001.tmp, IXP002.tmp etc with the number rising with each new folder created when a new exe is executed
Ok, I found my problem with where the temp files unpacked to when an EXE is run.
I had used capital letters in the path to my ramdrive temp files. Fixed it and now the exe temp files go to my ramdrive as expected. This would not have affected users who use this bas file, as it was a mistake on my PC settings only. The temp files will go wherever a users temp files usually go under "Environment variables" section of Performance tab. I believe the default is c:\Temp, or c:\TMP (I could be wrong about that though)
Also, once the running EXE file is closed, the temp files get deleted (I checked) Good news. No worries of the temp files piling up taking up room on a drive.
Hey guys and gals can I get a little feedback?
What OS's is this working on?
Has anyone got it working in Linux/WINE?
Any problems using it?