Re: Native Access
Posted: Sat Sep 01, 2018 1:00 pm
Thank you so much! I was just puzzling over the crashes trying to get my Reaktor extras loaded.
The Windows version (in winecfg) should be Windows 7 or above and not Windows XP.Wakellor wrote:Hi,
I've tried your method, @ubunutuuser, but I get the error "Installation cannot proceed, your operating system is not supported. Please check the minimum requirements" after the InstallAware Wizard...
Of course this could just be because my specs aren't good enough, but could it instead be my wine settings? Do I need to set the installer to Windows 7 or similar? Any extra overrides? (I'm quite new to overrides and don't fully understand them yet)
I've got 2.9GB RAM and 2x Celeron Dual-Core T3500 @ 2.10 GHz. I'm using Manjaro Linux.
PS: Does anyone know what the incompatible iso mounter is? And if so, is there a way to fix it?
Which one? There are three options:Install Visual C++ redist
Code: Select all
vcredist_arm.exe (1.4 MB)
vcredist_x64.exe (6.9 MB)
vcredist_x86.exe (6.2 MB)
Hi @ubuntuuser. Sorry I took so long to reply, but it worked fine and even though I didn't see this, I managed to work out the Windows 7 thing. Thanks for your help!ubuntuuser wrote:The Windows version (in winecfg) should be Windows 7 or above and not Windows XP.Wakellor wrote:Hi,
I've tried your method, @ubunutuuser, but I get the error "Installation cannot proceed, your operating system is not supported. Please check the minimum requirements" after the InstallAware Wizard...
Of course this could just be because my specs aren't good enough, but could it instead be my wine settings? Do I need to set the installer to Windows 7 or similar? Any extra overrides? (I'm quite new to overrides and don't fully understand them yet)
I've got 2.9GB RAM and 2x Celeron Dual-Core T3500 @ 2.10 GHz. I'm using Manjaro Linux.
PS: Does anyone know what the incompatible iso mounter is? And if so, is there a way to fix it?
In general, Wine can't handle Windows physical/hardware device drivers because it's not Windows, so a Windows Nvidia video driver won't work with Wine and the Native Access iso mounter driver is probably similar and so it causes a crash/hang.
That means that the downloaded iso file has to be fished out of wherever Native Access downloaded it to and then manually mounted and then installed (details in one of my above posts).
After that, Native Access will think everything was installed ok when it's started up again.
Trouble with Native Access iso downloads can even happen using Windows and some Windows users do the manual iso mounting method to get around it, so it's not that unusual to do it that way, it's just that on Linux it needs to be done that way.
Native access might need a msvcp140.dll override to run.
Overrides are just real Windows dlls that replace Wines inbuilt dlls which might lack some functions.
The way to install a dll override is to copy the real Windows dll (ie msvcp140.dll) to ~/.wine/drive_c/windows/system32 and then (maybe optionally) override the dll to be native using the winecfg Libraries option (ie just type in msvcp140 in the winecfg Libraries tab and then hit Add).
Hey, I wanted to say thank you for your thorough reply. I haven't gotten a chance yet to try it and likely won't this weekend, but I'll let you know. I'm actually planning on reinstalling Debian and staying on the "Stable" track. I took my install over to "Testing" track back in Novemberish thinking the latest packages would be benficial and it's worked well up until recently, but some other packages wound up broken in the last month, such as Carla.glowrak guy wrote: ↑Fri Feb 21, 2020 4:24 pm I'm a reaper/wine-staging user, with K6 running well in Ubuntu Studio 19.10
Try renaming .wine folder to something else, and do a new download and install
of wine-staging, new version is currently around 5.2 In winecfg panel, configure wine
as win 10. Then download and install the latest Native Access again.
If it's working, reinstall the latest Kontakt
and libs. Use LinVst plugin wrapper to create a Kontakt.so,
for use in linux daws, make sure the kontakt .dll and .so are in the same folder,
and the folder is in the vst scan path.
linvst downloads and docs: https://github.com/osxmidi/LinVst
If it still fails,
Install mfc42 and mfc42u 32bit dlls into
/home/you/.wine/drive_c/windows/syswow64
After renaming the wine mfc140.dll, Install the real mfc140.dll into
/home/you/.wine/drive_c/windows/system32, and use the libraries tab
in the winecfg panel, to select it as an over-ride. (just type mfc140
without the extension, into the dialog box, and click the apply button)
Do you have multiarch enabled? from the wine wiki
"On 64-bit systems you should enable a 32-bit architecture for multiarch. This is needed for running 32-bit Windows applications (many modern apps are still 32-bit), but also for large parts of the Windows subsystem itself. If in doubt, you do need it!
You can identify your architecture with the following command:
dpkg --print-architecture
E.g. for amd64 (which most users have) you need i386. Enable it with the following command:
sudo dpkg --add-architecture i386 && sudo apt update"
-------------------------------------------------------------------------
Once I get enough NI products installed, I stop all updates on wine
and NI products, just use them till your drive heads melt, and if you want more,
put them on a new linux in a fresh external drive. There's so much
going on that is so easily derailed, it's the most peaceful
and productive strategy. I think there is an ENV variable that can be set
to stop Native Access from attempting auto-updating, but I don't have
it at hand. I've seen it mentioned in the support docs on their website,
but things may have changed due to the 2019 layoffs.
You could also try the latest Ubuntu Studio, NA and NI products
are working well for me in that environment.
Cheers
Thanks again for your help. I was able to get it running, and Kontakt Player as a 32-bit plugin both under Carla and VeSTige. However I still can't get several of the products to install because they're shipped as an ISO, and I'm still not having any luck getting NA's ISO mounter to run; were you also able to get a solution going on that?glowrak guy wrote: ↑Fri Feb 21, 2020 4:24 pm I'm a reaper/wine-staging user, with K6 running well in Ubuntu Studio 19.10
Try renaming .wine folder to something else, and do a new download and install
of wine-staging, new version is currently around 5.2 In winecfg panel, configure wine
as win 10. Then download and install the latest Native Access again.
If it's working, reinstall the latest Kontakt
and libs. Use LinVst plugin wrapper to create a Kontakt.so,
for use in linux daws, make sure the kontakt .dll and .so are in the same folder,
and the folder is in the vst scan path.
linvst downloads and docs: https://github.com/osxmidi/LinVst
If it still fails,
Install mfc42 and mfc42u 32bit dlls into
/home/you/.wine/drive_c/windows/syswow64
After renaming the wine mfc140.dll, Install the real mfc140.dll into
/home/you/.wine/drive_c/windows/system32, and use the libraries tab
in the winecfg panel, to select it as an over-ride. (just type mfc140
without the extension, into the dialog box, and click the apply button)
Do you have multiarch enabled? from the wine wiki
"On 64-bit systems you should enable a 32-bit architecture for multiarch. This is needed for running 32-bit Windows applications (many modern apps are still 32-bit), but also for large parts of the Windows subsystem itself. If in doubt, you do need it!
You can identify your architecture with the following command:
dpkg --print-architecture
E.g. for amd64 (which most users have) you need i386. Enable it with the following command:
sudo dpkg --add-architecture i386 && sudo apt update"
-------------------------------------------------------------------------
Once I get enough NI products installed, I stop all updates on wine
and NI products, just use them till your drive heads melt, and if you want more,
put them on a new linux in a fresh external drive. There's so much
going on that is so easily derailed, it's the most peaceful
and productive strategy. I think there is an ENV variable that can be set
to stop Native Access from attempting auto-updating, but I don't have
it at hand. I've seen it mentioned in the support docs on their website,
but things may have changed due to the 2019 layoffs.
You could also try the latest Ubuntu Studio, NA and NI products
are working well for me in that environment.
Cheers
Code: Select all
mount -t udf file.so -o unhide /mnt
Cool, that's good news. I have a bunch of NI stuff that never gets used because I seldom boot to Windows, and I wasn't able to get it running on Debian. What version of WINE are you using?Wakellor wrote: ↑Fri Jul 24, 2020 6:15 pm Hi guys,
I have a really cool update for you!
Today, I decided to change 'Native Access.exe's OS mode to 'Windows 10' in winecfg.... and... it works!
Native Access updated itself (WITHOUT CRASHING!!!) and updated all the plugins I had without crashing too... I checked the Downloads folder while the updates were downloading and the plugin/library files are no longer ISOs, but ZIPs!
It works perfectly now so no moreever againCode: Select all
mount -t udf file.so -o unhide /mnt
I'm still getting the dreaded "Installation failed: Error while mounting disk image." I looked at my downloads and they're still coming in as iso's.Wakellor wrote: ↑Fri Jul 24, 2020 6:15 pm Hi guys,
I have a really cool update for you!
Today, I decided to change 'Native Access.exe's OS mode to 'Windows 10' in winecfg.... and... it works!
Native Access updated itself (WITHOUT CRASHING!!!) and updated all the plugins I had without crashing too... I checked the Downloads folder while the updates were downloading and the plugin/library files are no longer ISOs, but ZIPs!
It works perfectly now so no moreever againCode: Select all
mount -t udf file.so -o unhide /mnt