![]() This has been installed for less than 48 hours, so early days. I’ve not seen any of this behaviour as yet running within Parallels. One of my colleagues has been running FileMaker within Windows 11 on a Surface Pro X and has had some rendering issues that appear like a pinprick through FileMaker to other running apps. I do have a snapshot where I can revert to the Windows 10 option, but so far I see no need. My main tools being Office, FileMaker and Sequel Server Management Studio all appear to be running fine and I’ve used it today as part of a client’s FMP v15 to v19 upgrade. To be fair, I haven’t tried it for ages, so it is possible an earlier update resolved the problem. I’m pleased to report that so far, so good and even FileMaker Pro 16 Advanced is now running, which had given problems before. ![]() Yesterday, I was taken slightly by surprise when the Windows update and subsequent restart resulted in the upgrade to Windows 11. Having been running Windows Insider Preview ARM64 in Parallels 16 on my M1 MacBook Pro for some months now, I’ve repeatedly mentioned how impressive this has been in terms of performance and allowing me to run most versions of FileMaker backwards to v15 Advanced to support those clients who have not yet updated to v19.
0 Comments
Leave a Reply. |