Suddenly Proton16 compiles but no HEX file is being created?

[trastikata]

Hello all,

I am facing a very strange issue - Proton16 compiles successfully but doesn't create a HEX file. It seems the issue appeared after installing latest Windows 10 update KB5034441 but I can't confirm it for certain and it might not be related at all.

What is even odd, it seems either no HEX file is created or only "a.hex" being created.

I've tried rebooting, I've reinstalled Proton ... no change.

Any ideas? ... I am short of trying full Windows installation

[John Lawton]

Not sure it is related, but I suggest an internet search for KB5034441 which appears to be 'buggy'. Maybe check your hard drive free space too as there is some issue with the recovery partition size If I skim read right. Can you 'undo' the KB5034441 update till they fix it?

Good luck.

John

[trastikata]

Thank you John, first thing I did was to remove the update, but it didn't help ... seems I'll have to re-install Windows next weekend if don't find fix till then.

[trastikata]

Found a workaround - running the IDE as administrator solves the issue, however I am not sure for what changed after the Windows update that could have cause it.

[charliecoutas]

Does the compiler say "Creating Asm. Please wait." after it has compiled it? (When not in Admin mode).

Charlie

[trastikata]

Does the compiler say "Creating Asm. Please wait." after it has compiled it? (When not in Admin mode).

Hi Charlie,

yes, it does, then I see optimizing, then "Linking.." and then "Creating Hex file", however I don't see the file in the project directory and file search through the SSD returns nothing. Sometimes I see appearing "a.hex" file in the project folder, but not always.

AS John suggested I did some I-net search about the update and it seems to be a buggy security update, not sur though what changed after installation.

[John Lawton]

From what you say about requiring Admin mode, perhaps something to do with file/folder permissions. It might require command line stuff to examine and fix these. Worth trying instead of going the long route via a reinstall just to fix permissions.

[John Lawton]

Actually it looks like File Explorer will do the job. This article relates to Win 11 but should help: https://medium.com/@bardimintang/how-to-reset-ntfs-permissions-files-and-folders-to-default-in-windows-11-c797aca12360

[top204]

The compiler has its "User" folder within a directory that 'should' have full permissions all the time (C:\Users\User Name\PDS\User\), but with the recent versions of windows and their, mostly, unnecessary updates, you can never tell anymore. Compiled files need to be in an accessible folder because the compiler needs to erase, rename, then re-write files while it is compiling, and so does the assembler. So in your case, the assembler has not been able to create the hex file, or the assembled hex file has not been able to be renamed by the compiler.

So what was once an accessible folder has become a non-accessible folder on you machine, and this is where the original ".bas" file is held.

You can go into the ProtonIDE folder, and right click on the "ProtonIDE.exe" file and set it to run as admin all the time, by right clicking on it, then properties, then compatability, and tick it to always run as admin.

Many years ago, from Windows 7 onwards, I stopped updating windows because every update actually caused more problems than they solved, especially with windows 10, as I found out with my wife's laptop a few months ago that now runs a lot slower than it used to do before it updated, and I mean a "lot" slower. :-) I'm going to have to remove the windows 10 OS and replace it beccause the update has done so much harm to it. But never again, because I will go into the innards of windows 10 and make sure updates are permanently switched off. :-)

And many, many thanks for the load of devices that arrived today Dyanko, they are very much appreciated, and will allow me to create more devices for the compiler.

[trastikata]

Thank you all for the help. I don't want to start playing with the folder permissions because I might make it worse. For the moment running Proton as admin works for me so I won't have to re-install Windows.

Les, I am happy to hear they will be useful.

[John Lawton]

Thing is you might run into issues with other programs and their data if the user directory permissions aren't right, so I would suggest that you do fix the permissions.

If you aren't sure what they should be, look at another PC if you have one and copy that.

John

[trastikata]

Thing is you might run into issues with other programs and their data if the user directory permissions aren't right, so I would suggest that you do fix the permissions.

Thank you John. I've already ran into troubles with another important program and any attempt to install new programs return a file errors ... I guess I'll re-install Windows this weekend ... M$, no good 

[John Lawton]

Sorry to hear that



John

[GDeSantis]

This is one of many online sites that discuss the Windows 10 Clean Install process.

https://www.youtube.com/watch?v=dkYH5kxGGOU