Hello everyone
I finally managed to install windows on my old laptop, but I had to install an x64 version
So that is my question ... I've tried the drivers from version 1.0 and 1.1 to no success
However at least I see Noah Synth as device but it would not install the drivers even when I explicitly select them - "make sure it is designed to work with Windows for x64-based systems"
Does that mean I have to downgrade even more, get an older device to install XP on?
Any other ideas ? Thank you so much
Kind regards
Noah Synth Driver in WinXP x64
Re: Noah Synth Driver in WinXP x64
there was no need for 64bit drivers when the Noah was made.
-
- Posts: 2
- Joined: Tue Dec 19, 2023 12:45 pm
Re: Noah Synth Driver in WinXP x64
Thank you
Indeed, a windows xp in virtual box with correct USB port forwarding made everything work fine and can enjoy this (for me, new) piece of music making machine
I will look for more info on the forum ... for example the Pro One user interface is not showing up and trying to figure out if something is missing from the installation package v1.1
Indeed, a windows xp in virtual box with correct USB port forwarding made everything work fine and can enjoy this (for me, new) piece of music making machine

I will look for more info on the forum ... for example the Pro One user interface is not showing up and trying to figure out if something is missing from the installation package v1.1
Re: Noah Synth Driver in WinXP x64
I have a very smiliar problem. I installed Noah V1.1 via WinXP compatibility mode. It runs ver well and I can start all synth-remotes. Only thing is the driver. I get no connection with my Noah EX (USB Mode is Set to Windows) and I have no option to run the USB driver (cwusbaud.inf) in WinXP compatibility mode. How do I get the connection to work?
Re: Noah Synth Driver in WinXP x64
you can't. Creamware went out of business in 2007.
in fact, the remote software really doesn't work in a virtual box or in compatibility mode. it will probably work well enough to use presets, but as to real-time streams, no way.
do NOT attempt to update firmware using anything newer than XP. using a virtual machine or compatibility mode will result in a brick!
in fact, the remote software really doesn't work in a virtual box or in compatibility mode. it will probably work well enough to use presets, but as to real-time streams, no way.
do NOT attempt to update firmware using anything newer than XP. using a virtual machine or compatibility mode will result in a brick!
- Bud Weiser
- Posts: 2860
- Joined: Tue Sep 14, 2010 5:29 am
- Location: nowhere land
Re: Noah Synth Driver in WinXP x64
Just go and use and/or buy an "older" desktop or laptop running WinXP and install the Noah v1.1 software incl. drivers.
In WinXP SP3, disable Windows driver signing permanently in "My Computer > Properties > Hardware" and before installing the Noah drivers.
It works here flawlessly w/ an old Pentium 4 2.6GHz desktop, WinXP Pro SP3 as also using an Acer laptop which originally came w/ Win Vista.
When I installed Win XP on this laptop, I was able using the 32Bit Vista drivers for the Acer hardware still since there were no WinXP drivers available at all.
Perfect combo w/ my NoahEX USB, Wave and ASIO drivers working perfect.
Hey, you cann buy such laptops in working condition for 30-40 bucks.
No need to wrap your head around installing old software in virtual machines on modern computers.
The only device not working 100% as it should when using Noah standalone and without using the software editor is Prophet5.
The latest available Noah version has a bug preventing from in depth synth editing using Noah´s frontpanel controls and menue diving ONLY.
So,- I´m still looking for an older installer version not introducing this bug.

Bud
- Bud Weiser
- Posts: 2860
- Joined: Tue Sep 14, 2010 5:29 am
- Location: nowhere land
Re: Noah Synth Driver in WinXP x64
Hi Eisblau !
Seems something went wrong with keyfile import.
ONLY use the flashtool and .dmp files when urgently necessary.
There are no device keys included in these .dmp files.
These 2 files just only install the factory setup or an extended setup already containing formerly optional devices, except Prophet5 which is still optional.
Which to install and use depends on which device activation keys you own.
Upgrading the system software to latest available is the other reason to perform a re-flash.
So, be sure to run the latest system software on your Noah.
Have in mind re-flashing Noah is on your own risk and might render it being a brick when something goes wrong.
OTOH, I myself, I did it sucessfully,- and 3 times.
It seems it isn´t necessary to re-flash your Noah ´cause it runs and,- as you say,- works together w/ the Remote Editor Software.
When IRC,- the .allkeys files doesn´t exist anymore and now are .rgy files.
Did you get keys from Sonic Core or did you get keys from previous owner of your Noah ?
The keyfile should match your Noah´s hardware serial number which is printed on the sticker on the backpanel.
I only mention ´cause you say it´s been greyed out in your Noah registry window.
You can import an already complete keyfile,- or device keys one by one when using the .oxe files,- by using copy & paste.
I myself used keys I luckily received from Sonic Core.
AFAIR, the key import didn´t work by drag ´n drop here,- it´s a copy & paste routine instead,- and I too had to experiment a bit how the copy ´n paste routine really works w/ Noah.
It might behave sluggish and might need a repeat until being successful.
I believe it didn´t work w/ mouse right-click and then insert and I had to use the keyboard control "C" and "V" commands and left click (sometimes several times) into the related area before using control V to import the key.
Here is how it should look after successful import,-
good luck,-
Bud
Seems something went wrong with keyfile import.
ONLY use the flashtool and .dmp files when urgently necessary.
There are no device keys included in these .dmp files.
These 2 files just only install the factory setup or an extended setup already containing formerly optional devices, except Prophet5 which is still optional.
Which to install and use depends on which device activation keys you own.
Upgrading the system software to latest available is the other reason to perform a re-flash.
So, be sure to run the latest system software on your Noah.
Have in mind re-flashing Noah is on your own risk and might render it being a brick when something goes wrong.
OTOH, I myself, I did it sucessfully,- and 3 times.

It seems it isn´t necessary to re-flash your Noah ´cause it runs and,- as you say,- works together w/ the Remote Editor Software.
When IRC,- the .allkeys files doesn´t exist anymore and now are .rgy files.
Did you get keys from Sonic Core or did you get keys from previous owner of your Noah ?
The keyfile should match your Noah´s hardware serial number which is printed on the sticker on the backpanel.
I only mention ´cause you say it´s been greyed out in your Noah registry window.
You can import an already complete keyfile,- or device keys one by one when using the .oxe files,- by using copy & paste.
I myself used keys I luckily received from Sonic Core.
AFAIR, the key import didn´t work by drag ´n drop here,- it´s a copy & paste routine instead,- and I too had to experiment a bit how the copy ´n paste routine really works w/ Noah.
It might behave sluggish and might need a repeat until being successful.
I believe it didn´t work w/ mouse right-click and then insert and I had to use the keyboard control "C" and "V" commands and left click (sometimes several times) into the related area before using control V to import the key.
Here is how it should look after successful import,-
good luck,-

Bud