macOS 10.15 Catalina on Unsupported Macs

[Larsvonhier]

El Catalina!

or - how about a small problem solved in the realm of "Backing up with Time Machine from an (unsupported) Catalina client to an (unsupported) Mac Pro running as a network server" ?

Hop over here to read about the issue and solution! Might be of interest to anyone running the full old v5.2 of Apple´s server application.

 

[cliener]

Hey all,
Before I go too far, thanks for everyone’s work in giving life to old machines. Your efforts are very much appreciated.
I have a Mac Pro 3,1 running Mojave and I’m currently trying to upgrade to Catalina. I created a boot drive using the latest Catalina Patcher (1.3) with a freshly downloaded copy of the OS.
After booting to recovery, the install goes as normal until the post boot install fails with an error: “macOS could not be installed on your computer. The operation could not be completed. (com.apple.osinstall error -30) Quit the installer to restart the computer and try again.”

Any suggestions for how I can proceed?

 

[Larsvonhier]

Have you set the date/time to today´s match? If not, try that i.e. from terminal.
If it´s set correctly, and does not install either, try setting it back to some date in Sept. 2019 - you might have run into the invalidated certificate problem, depending what "fresh copy" your downloader actually got.

 

[GDMSR]

depending what "fresh copy" your downloader actually got.

Slightly worrying remark, as I thought the Patcher tool downloaded directly from Apple, and would therefore always be up-to-date? Perhaps I'm being naïve?

 

[StarIlia]

Hello! Please help. Installed on your MacBook Pro 2009 macosx Catalina using a patch from dosdude 1, and got cyclical reboots. The laptop can work for about 20 minutes, and can immediately go to reboot. Everything is fine with Mojave installed. The error is as follows: panic (cpu 0 caller 0xffffff8001e689ca): Kerneltrap at 0xffffff7f82f22f2d, type 14=page fault. Help to understand please.

 

[Larsvonhier]

Slightly worrying remark, as I thought the Patcher tool downloaded directly from Apple, and would therefore always be up-to-date? Perhaps I'm being naïve?

Not much to worry about. Usually, the download from Apple is the latest match for your system. It might fetch differing versions depending on your setting of the software-catalog URL (i.e. for developers or public beta user settings). You can check the installer version with the listing on page #1 of this thread to see what you actually got.
[automerge]1579180467[/automerge]

Hello! Please help. Installed on your MacBook Pro 2009 macosx Catalina using a patch from dosdude 1, and got cyclical reboots. The laptop can work for about 20 minutes, and can immediately go to reboot. Everything is fine with Mojave installed. The error is as follows: panic (cpu 0 caller 0xffffff8001e689ca): Kerneltrap at 0xffffff7f82f22f2d, type 14=page fault. Help to understand please.

You could try to post the complete post-mortem dump of the kernel panic here - perhaps it is related to some 3rd party extension or startup daemon that is present from Mojave times that KPs now.
What you can also try if you upgraded your Mojave installation instead of fresh installation (which normally works great, I´ve done so multiple times on many machines): Install a fresh copy i.e. on an external drive (Firewire or USB) and see if you can get a stable setup then?
Intermediate step: Use your buggy installation (?) and set up a new fresh user account, use that for a while to see if things are good there...

 

[Tim Thomason]

Thank you

it did not work for me... I guess ill have to wait on the patch installer from dosdude1.
thxs for all your help

 

[deeveedee]

Unfortunately, the legacy graphics patch modifies some core system files (including GPUSupport, OpenGL, CoreDisplay, SkyLight, and IOSurface) so a Metal-supported card will most likely not work anymore. You should perform a fresh install of Catalina over your existing copy. You won't lose any files.

Thank you for that very thorough response, @ASentientBot ! There's more under the hood than I thought - now I'm even more impressed with this Catalina Patcher! I feel prepared for the RX580 install and my MBP6,2 is running Catalina perfectly. Thank you!

 

[StarIlia]

Not much to worry about. Usually, the download from Apple is the latest match for your system. It might fetch differing versions depending on your setting of the software-catalog URL (i.e. for developers or public beta user settings). You can check the installer version with the listing on page #1 of this thread to see what you actually got.
[automerge]1579180467[/automerge]

You could try to post the complete post-mortem dump of the kernel panic here - perhaps it is related to some 3rd party extension or startup daemon that is present from Mojave times that KPs now.
What you can also try if you upgraded your Mojave installation instead of fresh installation (which normally works great, I´ve done so multiple times on many machines): Install a fresh copy i.e. on an external drive (Firewire or USB) and see if you can get a stable setup then?
Intermediate step: Use your buggy installation (?) and set up a new fresh user account, use that for a while to see if things are good there...

I tried to do a clean installation - completely formatted the disk and installed the system. not help.

"
panic(cpu 0 caller 0xffffff8001e689ca): Kernel trap at 0xffffff7f82f22f2d, type 14=page fault, registers:


CR0: 0x0000000080010033, CR2: 0xffffef7f82ff6c50, CR3: 0x0000000179ba1000, CR4: 0x00000000000026e0


RAX: 0xffffef7f82ff6af8, RBX: 0xffffff8012b8f200, RCX: 0xffffff80133d9000, RDX: 0x0000000000000000


RSP: 0xffffff910e163b90, RBP: 0xffffff910e163bd0, RSI: 0x0000000000000024, RDI: 0xffffff801347cb40


R8: 0x0000000000000000, R9: 0xffffff802249ca90, R10: 0x000000044b82fa08, R11: 0x0000000000000000


R12: 0x15cc7d3c68c8ea22, R13: 0x0000000000000000, R14: 0x15cc7d3c690625a8, R15: 0x0000000000000024


RFL: 0x0000000000010282, RIP: 0xffffff7f82f22f2d, CS: 0x0000000000000008, SS: 0x0000000000000010


Fault CR2: 0xffffef7f82ff6c50, Error code: 0x0000000000000000, Fault CPU: 0x0, PL: 0, VF: 1





Backtrace (CPU 0), Frame : Return Address


0xffffff910e1635f0 : 0xffffff8001d3f98b


0xffffff910e163640 : 0xffffff8001e76c15


0xffffff910e163680 : 0xffffff8001e6861e


0xffffff910e1636d0 : 0xffffff8001ce6a40


0xffffff910e1636f0 : 0xffffff8001d3f077


0xffffff910e1637f0 : 0xffffff8001d3f45b


0xffffff910e163840 : 0xffffff80024d2d89


0xffffff910e1638b0 : 0xffffff8001e689ca


0xffffff910e163a30 : 0xffffff8001e686c8


0xffffff910e163a80 : 0xffffff8001ce6a40


0xffffff910e163aa0 : 0xffffff7f82f22f2d


0xffffff910e163bd0 : 0xffffff7f82f15e6d


0xffffff910e163d50 : 0xffffff8001fcde12


0xffffff910e163dc0 : 0xffffff8001fbee6e


0xffffff910e163e20 : 0xffffff80022b8740


0xffffff910e163ee0 : 0xffffff80022b8a14


0xffffff910e163f40 : 0xffffff800239b999


0xffffff910e163fa0 : 0xffffff8001ce7206


Kernel Extensions in backtrace:


com.apple.filesystems.apfs(1412.11.7)[B26D7DE6-BE2D-3E44-B334-1346AEC6C3BB]@0xffffff7f82ed6000->0xffffff7f82ffafff


dependency: com.apple.kec.corecrypto(1.0)[263BCEB0-E4C5-3540-9E03-CC1F0A4D5BDF]@0xffffff7f8269f000


dependency: com.apple.driver.AppleEffaceableStorage(1.0)[D4D0276C-28F7-3878-AC53-86A1134225E0]@0xffffff7f82e82000


dependency: com.apple.iokit.IOStorageFamily(2.1)[CAC103D2-4533-3A81-8190-D0133B4F8626]@0xffffff7f82665000





BSD process name corresponding to current thread: WhatsApp


Boot args: -no_compat_check





Mac OS version:


19A583





Kernel version:


Darwin Kernel Version 19.0.0: Wed Sep 25 20:18:50 PDT 2019; root:xnu-6153.11.26~2/RELEASE_X86_64


Kernel UUID: 70EDD61F-86EE-3E1B-873F-98D909B78160


Kernel slide: 0x0000000001a00000


Kernel text base: 0xffffff8001c00000


__HIB text base: 0xffffff8001b00000


System model name: MacBookPro5,5 (Mac-F2268AC8)


System shutdown begun: NO


Panic diags file available: YES (0x0)





System uptime in nanoseconds: 233580430192


last loaded kext at 119607822920: com.adguard.nfext 26 (addr 0xffffff7f85074000, size 184320)


loaded kexts:


com.adguard.nfext 26


com.parrotgeek.SIPManager 1


@fileutil 20.036.15


>AudioAUUC 1.70


>!AGraphicsDevicePolicy 3.28.4


@AGDCPluginDisplayMetrics 3.28.4


>!AHV 1


@filesystems.autofs 3.0


|IOUserEthernet 1.0.1


|IO!BSerialManager 7.0.0f8


>pmtelemetry 1


>!AUpstreamUserClient 3.6.8


>!AHDAHardwareConfigDriver 281.52


>AGPM 110.23.46


>!AMikeyHIDDriver 131


@Dont_Steal_Mac_OS_X 7.0.0


@GeForceTesla 10.0.4


>AGDCBacklightControl 4.1.46


>!AHDA 281.52


>!AMikeyDriver 281.52


>!ABacklight 170.18


>SMCMotionSensor 3.0.4d1


@nvenet 2.0.22


>!ASMCLMU 212


>AirPort.Brcm4331 800.21.31


>!ALPC 3.1


>ACPI_SMC_PlatformPlugin 1.0.0


>!AFWOHCI 5.6.2


>!AFIVRDriver 4.1.0


>!A!ISlowAdaptiveClocking 4.0.0


@nvidia.NVDAStartup 14.0.0


>!AMCCSControl 1.5.6


>!UTCKeyEventDriver 255


>!UTCButtons 255


>!UTCKeyboard 255


|IO!BUSBDFU 7.0.0f8


>!AIR!C 360


>!U!SCoexistentDriver 489.11.2


>!UCardReader 489.11.2


@filesystems.apfs 1412.11.7


>!AFileSystemDriver 3.0.1


>!AVirtIO 1.0


@filesystems.hfs.kext 522.0.9


@!AFSCompression.!AFSCompressionTypeDataless 1.0.0d1


@BootCache 40


@!AFSCompression.!AFSCompressionTypeZlib 1.0.0


|SCSITaskUserClient 422.0.2


@private.KextAudit 1.0


>!AAHCIPort 341.0.2


>!ASmartBatteryManager 161.0.0


>!ARTC 2.0


>!AHPET 1.8


>!AACPIButtons 6.1


>!ASMBIOS 2.1


>!AACPIEC 6.1


>!AAPIC 1.7


>!A!ICPUPowerManagementClient 222.0.0


$!AImage4 1


@nke.applicationfirewall 302


$TMSafetyNet 8


@!ASystemPolicy 2.0.0


>!A!ICPUPowerManagement 222.0.0


|EndpointSecurity 1


>!AGraphicsControl 3.28.4


|IOAVB!F 800.17


@kext.triggers 1.0


>!ASSE 1.0


@plugin.IOgPTPPlugin 800.14


|IOEthernetAVB!C 1.1.0


|IOSkywalk!F 1


@nvidia.classic.NVDANV50HalTesla 10.0.4


@nvidia.classic.NVDAResmanTesla 10.0.4


>DspFuncLib 281.52


@kext.OSvKernDSPLib 529


|IOFireWireIP 2.3.0


@!AGPUWrangler 3.28.4


@!AGraphicsDeviceControl 3.28.4


>!ABacklightExpert 1.1.0


|IONDRVSupport 519.15


>!AHDA!C 281.52


|IOHDA!F 281.52


|IOAudio!F 300.2


@vecLib.kext 1.2.0


|IO80211!F 1200.12.2


>corecapture 1.0.4


>NVSMU 2.2.9


>IOPlatformPluginLegacy 1.0.0


>IOPlatformPlugin!F 6.0.0d8


>!ASMBusPCI 1.0.14d1


|IOFireWire!F 4.7.5


|IOSlowAdaptiveClocking!F 1.0.0


>!ASMBus!C 1.0.18d1


|IOGraphics!F 519.15


>!UMultitouch 264


|Broadcom!BHost!CUSBTransport 7.0.0f8


|IO!BHost!CUSBTransport 7.0.0f8


|IO!BHost!CTransport 7.0.0f8


|IO!B!F 7.0.0f8


|IO!BPacketLogger 7.0.0f8


>usb.IOUSBHostHIDDevice 1.2


>usb.!UHub 1.2


|IOUSBMass!SClass 4.0.4


>usb.cdc 5.0.0


>usb.networking 5.0.0


>usb.!UHostCompositeDevice 1.2


>!AXsanScheme 3


|IOSerial!F 11


|IOSurface 269.6


@filesystems.hfs.encodings.kext 1


|IOSCSIMultimediaCommandsDevice 422.0.2


|IOBD!S!F 1.8


|IODVD!S!F 1.8


|IOCD!S!F 1.8


|IOAHCISerialATAPI 268


|IOAHCIBlock!S 316.0.5


|IOAHCI!F 290.0.1


>usb.!UHostPacketFilter 1.0


|IOUSB!F 900.4.2


>usb.!UEHCIPCI 1.2


>usb.!UOHCIPCI 1.2


>usb.!UOHCI 1.2


>usb.!UEHCI 1.2


>!AEFINVRAM 2.1


>!AEFIRuntime 2.1


|IOSMBus!F 1.1


|IOHID!F 2.0.0


$quarantine 4


$sandbox 300.0


@Kext.!AMatch 1.0.0d1


>DiskImages 493.0.0


>!AFDEKeyStore 28.30


>!AEffaceable!S 1.0


>!AKeyStore 2


>!UTDM 489.11.2


|IOSCSIBlockCommandsDevice 422.0.2


>!ACredentialManager 1.0


>KernelRelayHost 1


>!ASEPManager 1.0.1


>IOSlaveProcessor 1


|IOTimeSync!F 800.14


|IONetworking!F 3.4


|IOUSBMass!SDriver 157.11.2


|IOSCSIArchitectureModel!F 422.0.2


|IO!S!F 2.1


|IOUSBHost!F 1.2


>!UHostMergeProperties 1.2


>usb.!UCommon 1.0


>!ABusPower!C 1.0


|CoreAnalytics!F 1


>!AMobileFileIntegrity 1.0.5


@kext.CoreTrust 1


|IOReport!F 47


>!AACPIPlatform 6.1


>!ASMC 3.1.9


>watchdog 1


|IOPCI!F 2.9


|IOACPI!F 1.4


@kec.pthread 1


@kec.Libm 1


@kec.corecrypto 1.0


"

 

[Larsvonhier]

I tried to do a clean installation - completely formatted the disk and installed the system. not help.

"
panic(cpu 0 caller 0xffffff8001e689ca): Kernel trap at 0xffffff7f82f22f2d, type 14=page fault, registers:


CR0: 0x0000000080010033, CR2: 0xffffef7f82ff6c50, CR3: 0x0000000179ba1000, CR4: 0x00000000000026e0


RAX: 0xffffef7f82ff6af8, RBX: 0xffffff8012b8f200, RCX: 0xffffff80133d9000, RDX: 0x0000000000000000


RSP: 0xffffff910e163b90, RBP: 0xffffff910e163bd0, RSI: 0x0000000000000024, RDI: 0xffffff801347cb40


R8: 0x0000000000000000, R9: 0xffffff802249ca90, R10: 0x000000044b82fa08, R11: 0x0000000000000000


R12: 0x15cc7d3c68c8ea22, R13: 0x0000000000000000, R14: 0x15cc7d3c690625a8, R15: 0x0000000000000024


RFL: 0x0000000000010282, RIP: 0xffffff7f82f22f2d, CS: 0x0000000000000008, SS: 0x0000000000000010


Fault CR2: 0xffffef7f82ff6c50, Error code: 0x0000000000000000, Fault CPU: 0x0, PL: 0, VF: 1





Backtrace (CPU 0), Frame : Return Address


0xffffff910e1635f0 : 0xffffff8001d3f98b


0xffffff910e163640 : 0xffffff8001e76c15


0xffffff910e163680 : 0xffffff8001e6861e


0xffffff910e1636d0 : 0xffffff8001ce6a40


0xffffff910e1636f0 : 0xffffff8001d3f077


0xffffff910e1637f0 : 0xffffff8001d3f45b


0xffffff910e163840 : 0xffffff80024d2d89


0xffffff910e1638b0 : 0xffffff8001e689ca


0xffffff910e163a30 : 0xffffff8001e686c8


0xffffff910e163a80 : 0xffffff8001ce6a40


0xffffff910e163aa0 : 0xffffff7f82f22f2d


0xffffff910e163bd0 : 0xffffff7f82f15e6d


0xffffff910e163d50 : 0xffffff8001fcde12


0xffffff910e163dc0 : 0xffffff8001fbee6e


0xffffff910e163e20 : 0xffffff80022b8740


0xffffff910e163ee0 : 0xffffff80022b8a14


0xffffff910e163f40 : 0xffffff800239b999


0xffffff910e163fa0 : 0xffffff8001ce7206


Kernel Extensions in backtrace:


com.apple.filesystems.apfs(1412.11.7)[B26D7DE6-BE2D-3E44-B334-1346AEC6C3BB]@0xffffff7f82ed6000->0xffffff7f82ffafff


dependency: com.apple.kec.corecrypto(1.0)[263BCEB0-E4C5-3540-9E03-CC1F0A4D5BDF]@0xffffff7f8269f000


dependency: com.apple.driver.AppleEffaceableStorage(1.0)[D4D0276C-28F7-3878-AC53-86A1134225E0]@0xffffff7f82e82000


dependency: com.apple.iokit.IOStorageFamily(2.1)[CAC103D2-4533-3A81-8190-D0133B4F8626]@0xffffff7f82665000





BSD process name corresponding to current thread: WhatsApp


Boot args: -no_compat_check





Mac OS version:


19A583





Kernel version:


Darwin Kernel Version 19.0.0: Wed Sep 25 20:18:50 PDT 2019; root:xnu-6153.11.26~2/RELEASE_X86_64


Kernel UUID: 70EDD61F-86EE-3E1B-873F-98D909B78160


Kernel slide: 0x0000000001a00000


Kernel text base: 0xffffff8001c00000


__HIB text base: 0xffffff8001b00000


System model name: MacBookPro5,5 (Mac-F2268AC8)


System shutdown begun: NO


Panic diags file available: YES (0x0)





System uptime in nanoseconds: 233580430192


last loaded kext at 119607822920: com.adguard.nfext 26 (addr 0xffffff7f85074000, size 184320)

Hm. At least WhatsApp and the Adguard kernel extension are not part of a clean install.
Other things hint to perhaps a faulty hard drive flex cable that triggers APFS I/O errors - that might be so with Mojave also but is handled differently (more critically) with Catalina.
Is there a specific reason you stick to 10.15.0 and do not use the final 10.15.2 ?

 

[0134168]

hello..
can you tell me how you did that, the installer i have only shows the 10.15.2 to install??

I said "run".
[automerge]1579199084[/automerge]

Hey all,
Before I go too far, thanks for everyone’s work in giving life to old machines. Your efforts are very much appreciated.
I have a Mac Pro 3,1 running Mojave and I’m currently trying to upgrade to Catalina. I created a boot drive using the latest Catalina Patcher (1.3) with a freshly downloaded copy of the OS.
After booting to recovery, the install goes as normal until the post boot install fails with an error: “macOS could not be installed on your computer. The operation could not be completed. (com.apple.osinstall error -30) Quit the installer to restart the computer and try again.”
View attachment 888874
Any suggestions for how I can proceed?

Did you patch the ROM?

 

[TimothyR734]

it did not work for me... I guess ill have to wait on the patch installer from dosdude1.
thxs for all your help

the other thing you could try is if you want a dev beta profile go to beta profiles or the public beta which should be released soon go to apple beta program and enroll your mac and it is important that you apple the second patch before restarting your mac to install the update. If for some reason your mac boots back into Catalina then the update should pop back up asking you to restart then try to apple the second patch I posted again then restart and install the update but let it do its thing

 

[Tim Thomason]

the other thing you could try is if you want a dev beta profile go to beta profiles or the public beta which should be released soon go to apple beta program and enroll your mac and it is important that you apple the second patch before restarting your mac to install the update. If for some reason your mac boots back into Catalina then the update should pop back up asking you to restart then try to apple the second patch I posted again then restart and install the update but let it do its thing

I have the public beta already, it say dev beta program in the software update pref panel.

 

[TimothyR734]

try running the swupatch again it should find the update make sure you enter your password when asked and yes twice when asked

 

[Tim Thomason]

try running the swupatch again it should find the update make sure you enter your password when asked and yes twice when asked

I will try it again, thxs

 

[iMac-iPad]

I installed macOS 10.15.2 and it is fine enjoying now.

Thank you @dosdude1 and all team members!

 

[Pinarek]

are you using the software update pref Panel for the updates??

No, the new update is always displayed automatically on the unsupported laptop.
I don't need a sw tool or anything else.
And I will continue, as I wrote here some time ago.
That was all and everything is well updated.

 

[cliener]

Have you set the date/time to today´s match? If not, try that i.e. from terminal.
If it´s set correctly, and does not install either, try setting it back to some date in Sept. 2019 - you might have run into the invalidated certificate problem, depending what "fresh copy" your downloader actually got.

I checked the date which was correctly set but then changed it to mid-September 2019 and still no luck.

Is there a log file I can reach to find out what failed?

 

[Tim Thomason]

I will try it again, thxs

It finally gave me the update.. thank you for the assist

 

[StarIlia]

Hm. At least WhatsApp and the Adguard kernel extension are not part of a clean install.
Other things hint to perhaps a faulty hard drive flex cable that triggers APFS I/O errors - that might be so with Mojave also but is handled differently (more critically) with Catalina.
Is there a specific reason you stick to 10.15.0 and do not use the final 10.15.2 ?

Unfortunately, I didn't save the reports after a clean installation. This is an error report after installing on top of Mojave. Therefore, traces of programs are visible. If we talk about failures in Mojave (with which I am writing now) - they do not exist at all... According to Catalina - installed all versions using the dosdude1 patch. This is just one of the reports after one of the crashes. The dosdude1 patch, as I understand it, downloads the latest version of Catalina. Due to the fact that there were many attempts on my part-I think I installed all versions... By the way, I tried to change the ssd disk itself - nothing changed. But maybe it's really about the cable.

By the way, I have already tried it-I installed Catalina on an external hard drive. The problem remained. So it's not about the hard drive cable...

 

[yurc]

I have out of a loop a while about Catalina, can someone explain me if this scenario possible?

1. Download Catalina and install on external SSD through my supported 2018 MacBook Pro
2. Set no compatibility check argument on target Mac Pro 5,1
3. Put installed SSD back
4. Apply some post installation to enable some features (Handoff, Airdrop), I have supported ac wi-fi cards
   
   

This should Catalina installed, right?

The problem, is software upgrades workaround with this setup worked?
When newer updates out, let says 10.15.3 public released.

1. I take out my Catalina boot SSD on my Mac Pro 5,1
2. Put them on exclosure and attach it again on my supported MacBook Pro 2018
3. Install updates on that SSD
4. Put it back on my Mac Pro

I know there’s patcher methods with built-in updater, or OpenCore using VM flag enable but for now I want keep vanilla as possible. Not mentioned I prefer OpenCore on my hackintosh instead of my MP.

 

[0134168]

I have out of a loop a while about Catalina, can someone explain me if this scenario possible?

1. Download Catalina and install on external SSD through my supported 2018 MacBook Pro
2. Set no compatibility check argument on target Mac Pro 5,1
3. Put installed SSD back
4. Apply some post installation to enable some features (Handoff, Airdrop), I have supported ac wi-fi cards
   

This should Catalina installed, right?

The problem, is software upgrades workaround with this setup worked?
When newer updates out, let says 10.15.3 public released.

1. I take out my Catalina boot SSD on my Mac Pro 5,1
2. Put them on exclosure and attach it again on my supported MacBook Pro 2018
3. Install updates on that SSD
4. Put it back on my Mac Pro

I know there’s patcher methods with built-in updater, or OpenCore using VM flag enable but for now I want keep vanilla as possible. Not mentioned I prefer OpenCore on my hackintosh instead of my MP.

That sounds good to me.

 

[Larsvonhier]

...
By the way, I have already tried it-I installed Catalina on an external hard drive. The problem remained. So it's not about the hard drive cable...

To rule out the internal drive cable, you´d also have to remove the internal drive completely, otherwise the file system there will be mounted, and indexing (spotlight) and other services will access it, still possibly causing the problem. But chances are, the cable might not be the culprit!
So...
Another thing to check: RAM integrity, just to rule out HW related failures.
Best option here would be to download the platform-independent RAM tester, burn it on CD, boot from it and let it run for a while (100% coverage of all different tests is normally not neccessary as RAM bit cell or addressing errors show up quite early).
Link here. Runs on all intel machines, PC and Macs. Free version of Memtest86 is sufficient.

 

[Bero]

MacBook Pro 15" Mid-2010, Catalina 10.15.2, DosDude patcher 1.3.0
NVIDIA GeForce GT 330M 256 MB
Intel HD Graphics 288 MB

I have problem with very slow maps.google.com, pretty unusable.
Did you have any solution to this problem?

 

[yurc]

That sounds good to me.

That’s great. Thank you for your confirmation.