(Today, 04:05 AM)eoredson Wrote:Whelp, arghh. Judging from the size of that compilelog.txt I'm guessing you are working with the 64-bit version. Have you tried the 32-bit version?(Today, 03:26 AM)JRace Wrote: Hmmmmmn.I normally restart Windows when a update icon on the taskbar indicates there is a update ready to install.
Okay, I'm out of ideas... except... when was the last time you shut down Windows completely and restarted?
Windows can start acting flaky if you run it for too long without a full restart. I once had a perfectly good compiler go bonkers and fail to create even the simplest executable.
Turned out it wasn't the compiler. It was Windows, which I had left running for about a month. I now try to remember to restart Windows at least once per week.
Otherwise I shutdown my computer Friday evening because I am not online on Saturdays..
(Today, 03:44 AM)Cobalt Wrote: I haven't installed anything to my C drive since the days of DOS 3.11! if I have any choice in the matter (and yes there is some software out there that still gives you a choice) it goes elsewhere, heck at one time I didn't even install the OS to my C drive! tended to confuse the crap out of viruses and hackers when the C drive was empty! I knew if I found anything there it was time to reformat and reinstall.
any hoot...
Comp errors on a fresh clean install(unpacking the zip\rar\7z\ect. is in fact installing) can typically mean an issue with anti-virus(might as well call those viruses anymore) and\or permission issues.(need to kick MS programmers in the neither regions for that headache)
I just downloaded and tried both x86 and x64 versions and had no issue with PRINT "Hello World" anyway. Small issue with the extraction of the Archive but didn't seem to affect anything for compilation. installed in G:\, Running Windows 10 on a slightly beefy Ryzen 9 cpu.
LOL.
I've never hesitated to use the C: drive, but I NEVER do things the way MS intended.
I hate installers and only use them when there is no choice. I've collected a set of small utilities that allow me to extract the files from most installers and test the software, then put it wherever I want. If software won't run without an official installation, then I often decide I don't want it around.
Heck, I once experimented with making a thumbdrive-portable version of Jacob Navia's build of the LCC compiler. For some unfathomable reason Navia built the compiler in the Microsoft way, using the Windows Registry to feed the compiler its essential location information. Environment variables, Jacob, environment variables! I FORCED that stupid build to work, using batch files to set the needed Registry keys, run the compiler, then delete the keys. FWIW it was a (somewhat spiteful) proof of concept. I have no need for THAT compiler.
I never use "Program Files" for manual "installs". I have my own directory layout for that. The neat thing about that arrangement is that I can zip the whole thing up and copy it to a new computer if/when it's needed, with my own self-written "install" utility to make the Start Menu & Send To links that I want.
"My Documents" is a dumping ground for stuff that I may or may not eventually email to someone. I never touch any of the "My" folders unless some annoying piece of software forces me to.