Has anyone loaded ReactOS and tried laz 32 bit apps on it?

[Jonax]

This spring I revisited the ReactOS and made a VM with QEMU/KVM under Debian. Managed to install and compile some but not all of my projects with the 32-bit Lazarus 3.6 for windows. As I recall it the debugger caused some issues so I turned it off. And for some reason I wasn't successful with 32-bit 4.0

I find ReactOS pretty cool so revived some ancient Delphi programs/games compiled under XP and now also the newer FPC/Lazarus code compiled on Virtual ReactOS. Is available in the XP/ReactOS section on my site if anyone want to try. Should run under ReactOS VM or XP, if anyone still got access to that. I suggest trying the Knight program/game, or Knight's Quest in Elephant Valley. Very modest system requirements 

[MarkMLl]

Did you use btrfs or FAT32 (see other postings in this thread)?

As discussed in a different thread I've been experimenting with WINE recently, and (I admit to my surprise) found the debugger fairly solid.

BUT I'm still on Lazarus 2.6 (FPC 3.2.2): the hype relating to later versions has gone over my head.

MarkMLl

[Jonax]

"Did you use btrfs or FAT32 (see other postings in this thread)?"

Had to check. I used whatever was the default at installation. Seems to be FAT32.

[MarkMLl]

I've just checked (more than anything else I was making sure that Qemu/KVM worked properly on Debian 13) and it appears that ReactOS 0.4.15 no longer has BtrFS support- at least in the visible installer etc.

As such, Lazarus 3.8 installed without problem on 16Gb FAT-32.

Updated: today's "nightly build" of 0.4.16 allows selection of filesystem type during installation (i.e. including BtrFS) but has definite quirks: among other things it took me several attempts to get two discs (BtrFS and FAT32) set up, and i don't know whether there's any sort of partitioner/formatter available from inside a running installation.

Attempting to install Lazarus into C:\Lazarus where c: is formatted as BtrFS was painful: it would spend roughly 30 seconds copying files then roughly 75 seconds thinking about life quietly. In the end I went out for a couple of hours, and when I got back it had stopped with the progress box announcing a CRC error, telling it to retry resulted in a declaration that "The media is write-protected" indicating a path on c:..

Installing into D:\Lazarus where d: is formatted as FAT-32 appears OK, although there might obviously be issues related to its "not being in the right place".

This suggests a serious issue with ReactOS's BtrFS implementation, but in line with my original bug report I feel this is something that the FPC community and maintainers need to be aware of.

MarkMLl

[PascalDragon]

This suggests a serious issue with ReactOS's BtrFS implementation, but in line with my original bug report I feel this is something that the FPC community and maintainers need to be aware of.

No. Again, the goal of ReactOS is binary compatibility to Windows. So there will not be a change to our installer as its something that needs to be fixed by ReactOS and ReactOS only.

[MarkMLl]

This suggests a serious issue with ReactOS's BtrFS implementation, but in line with my original bug report I feel this is something that the FPC community and maintainers need to be aware of.

No. Again, the goal of ReactOS is binary compatibility to Windows. So there will not be a change to our installer as its something that needs to be fixed by ReactOS and ReactOS only.

I said "be aware of", since the OS setup determines whether Lazarus will work.

In the past I've managed to work around this by mounting the FAT32 volume on c:\Lazarus, but when trying that with 0.4.16 (nightly build) it was apparent that either I've forgotten the incantation or it doesn't work.

I didn't ask the maintainers to do anything, and I definitely was not expecting you to do anything.

In practice, I'm able to blue-screen ReactOS 0.4.15 reproducibly with one specific program written using FPC/Lazarus which has a long history of working properly on Windows. I don't much relish looking for the cause, and I relish even less trying to convince the C++ users that maintain ReactOS why they should care about something written in an unfamiliar language.

MarkMLl