Lazarus 1.4.2 and Windows 10

[dalcymru]

'Upgrading' windows 7 to Windows 10, little did I expect to find ruined my Lazarus apps.  Because the new windows changed some files in my Lazarus home-projects directory during its self-installation, so they no longer appeared on my desktop and did not run when I tried to find the compiled .exe file on my hard drive, I tried to run the app from a backup on a usb dongle.  This ran, but form layouts needed adjustment.  However, when I loaded the project into lazarus, it would not compile, reporting errors because it was unable to delete various backup files.

Has anyone else experienced this, please, and how, if at all, did they 'cure' the problem?

[BitBangerUSA]

'unable to delete various backup files.'

seems to indicate you might want to try running Lazarus as Admin - if you haven't already.

the form layout needing adjustment is not surprising - i saw same-same with Windows 8.1.
i've got a new, fresh, *clean* install of Windows 10 but have not yet tried compiling one of my projects - maybe late night tonight...

[BitBangerUSA]

my project compiled as expected - no compile/link issues seen.

Lazarus 1.4.2 and Windows 10 Home - but again, this was a clean install of Windows, not an upgrade.

[rvk]

No problem whatsoever here with Windows 10 upgrade. In which directory are your own apps installed? In which directory is Lazarus installed? What error messages exactly are you getting with your own apps? What error messages exactly are you getting with recompiling in Lazarus?

[dalcymru]

Thanks to all for your interest and pointers.  It required 'Run as Administrator' to be set, and I found
https://technet.microsoft.com/en-us/magazine/ff431742.aspx as a useful guide to making Lazarus always run as administrator.

[rvk]

So you are going to run all your laz applications as administrator? I would find out why you get errors and adjust your program to work the correct way on Windows. I wouldn't feel happy to always run them as administrator (but maybe that's personal).

[marcov]

I don't understand fully, afaik Lazarus is nearly entirely in user writable directories.

Did you change user/create a new user while upgrading?

[minesadorada]

I had similar problems to @dalcymru with a simple msaccess-based app suite after upgrading from Win 7 to Win 10.

I upgraded Lazarus to the latest release which partially solved it, but 'clean up and build' was finally only effective when running Laz as an administrator.  I assume there were permission problems deleting older .ppus etc - but that's only a guess.

All good now - thanks for the link dalcymru.

[marcov]

It could mean that windows 10 zaps all filesystem permissions outside homedirs. Bad.

[rvk]

@minesadorada and @dalcymru... were you as user an "Administrator" or just plain "Standard user" who can't install programs?

I'm "Administrator" (not to be confused with the old Administrator-user) and have no problems after upgrading. I run Lazarus 1.4.2 and trunk in C:\Lazarus and C:\Dev\Lazarus as a normal user and have no need to "Run as Administrator".

It would be nice to know what files (and in which directories) gave you trouble.

[lainz]

Working perfectly here, the same lazarus win7 now win10 is fine.

[minesadorada]

@minesadorada and @dalcymru... were you as user an "Administrator" or just plain "Standard user" who can't install programs?

I'm "Administrator" (not to be confused with the old Administrator-user) and have no problems after upgrading. I run Lazarus 1.4.2 and trunk in C:\Lazarus and C:\Dev\Lazarus as a normal user and have no need to "Run as Administrator".

It would be nice to know what files (and in which directories) gave you trouble.

I log on as an 'administrator'

My app uses the GetConfigDir calls for data and logs to its own folder.

It was TAChart that tripped up the app - no idea why.

I am frankly amazed that the upgrade from Windows 7 to Windows 10 messed up a well-written (IMHO) Lazarus application.

[Thaddy]

Well, if TAChart uses a directory that has insufficient rights it may fail if it tries to write or read series data.

Just make sure that data/inifiles is stored in f.e. %HOMEDRIVE%\users\%USERNAME%\appdata\local\*

These are guidelines that aren't new, but few Pascalites (be it Delphinians or Free) adhere to them. Including component writers and maintainers!

[rvk]

Just make sure that data/inifiles is stored in f.e. %HOMEDRIVE%\users\%USERNAME%\appdata\local\*

Ieks...  And also don't use that one 

If you want to do it according to the guidelines you shouldn't append such "path variables" together. I've seen perfectly fine/official systems where the user directories are not on the %HOMEDRIVE% and appdata is also not standard across different Windows-versions.

You probably wanted to say: %LOCALAPPDATA% (local specific to that machine) or even %APPDATA% which is the "roaming" one for domain environments.

You can find a list on this wiki-site:
https://en.wikipedia.org/wiki/Environment_variable#Windows

[minesadorada]

Well, if TAChart uses a directory that has insufficient rights it may fail if it tries to write or read series data.

Just make sure that data/inifiles is stored in f.e. %HOMEDRIVE%\users\%USERNAME%\appdata\local\*

These are guidelines that aren't new, but few Pascalites (be it Delphinians or Free) adhere to them. Including component writers and maintainers!

For writeable config files I follow the wiki guidelines here: http://wiki.freepascal.org/Multiplatform_Programming_Guide#Configuration_files