This is the second time I've experienced this, with different versions of Lazarus on Windows XP 32 bit running as Guest on Virtualbox on a Ubuntu system.

The first version was Lazarus-1.0.7-40379-fpc-2.6.0-20130224-win32 and the program suddenly claimed that I had upgraded and wanted to upgrade the User preferences. After which the PAS file on the app I was working on contained 12Kb of zeros.

Now, Lazarus 1.1 r40379 FPC 2.6.1 i386-win32-win32/win64 is doing the same.

I was working on a significantly larger project, but the main PAS file, it's LFM Form descriptor and the .res, .lps, and .lpi have all had their content replaced with zeros.

Also several files in C:\Documents and Settings\dave\Local Settings\Application Data\lazarus have been corrupted.

EditorMacros.xml and environmentoptions.xml have both had their content replaced with zeros.

Is this a known issue?

Hi Dave.

I've had the same trouble some time ago and submitted the problem here. Unfortunately I'm not able to find the topic in this forum. It looks like it was before 2012.
I wonder if the name of one of the files was concerned. Maybe one with blakns in the name.
If I remember well I used this version too.

Antonio.

Le 07/10/2013 19:00, Dave Coventry a ?crit :

Hi Antonio,

The first one, with Lazarus-1.0.7-40379-fpc-2.6.0-20130224-win32, was with a very standard small App called 'pruler.lpi'. There was only one PAS unit and it was simply called 'Unit1.pas', so (in my case, anyway) there is unlikely to have been naming conflicts.

I'm wondering if it has something to do with the VirtualBox configuration as this doesn't seem to be a common experience amongst Lazarus users (from the response on here, anyway), although it's happened to me twice in the last week, on different Lazarus versions and on separate code projects.

Dave

Le 08/10/2013 10:14, Dave Coventry a ?crit :

I'm using VB a lot myself (home and at work) along with esxi (at work) and I haven't experienced such a problem, except some months (maybe even years) ago.
I do not rremember if Lazarus was involved or not. Win32 excepted (Vista box) all others (Linux64, Win64) are in esxi virtual machines.

configuration as this doesn't seem to be a common experience amongst Lazarus users (from the response on here, anyway), although it's happened to me twice in the last week, on different Lazarus versions

Same for me, until I decided to reinstall from blank. I think this was the solution but I'm not really sure.

Antonio.

Antonio Fortuny wrote

Same for me, until I decided to reinstall from blank. I think this was the solution but I'm not really sure.

Okay, I'll keep an eye on this and see if I can spot any common circumstances if it happens again. Fortunately the auto-Backup files meant that not too much was lost...