Miditzer 260 Corruption

Job one is installing the Miditzer and getting it configured
Post Reply
SteveM
Newbie
Posts: 23
Joined: Sun Apr 08, 2012 6:37 am
Spam Stopper: theatre organ
How many Style 216 did Wurlitzer make?: 12
Location: UK

Miditzer 260 Corruption

Post by SteveM » Tue Dec 06, 2016 3:29 pm

I have started a new topic because this relates mainly to the 260 but follows on from my 'New Set Up Miditzer 260 - Win 7 32Bit SP1Novation Launchpad and KeyB' topic, which is now working fairly well even down to the swell pedal.

I had previously downloaded the 260 but because of the complexity of getting the launchpad mapping to work, followed the advice and stuck with the 216 to iron out the problems. I am now again trying to set the 260 up but I am finding that there is something not right with the install.

I believe there may be corrupt hidden file that is not being deleted when I do I full uninstall because when I first re-install the 260 it loads and works from the PC keyboard (not even tried to connect the midi yet). However when I close it after the 1st time and then try and open it again later it will not run. I have run task manager and it does briefly display in the applications tab but disappears within about a second.

Are there any hidden files or registry settings I can locate and purge before trying another install from scratch? It appears something remains when removing the 260 that then stops it working after the initial launch.

Thanks for any advice

User avatar
Jim Henry
Admin Group
Posts: 6134
Joined: Mon May 23, 2005 11:44 pm
Spam Stopper: theatre organ
How many Style 216 did Wurlitzer make?: 12
Location: United States

Re: Miditzer 260 Corruption

Post by Jim Henry » Wed Dec 07, 2016 1:35 am

There is a special file that controls the 260SP Registration. But it is written by a third party software package and I don't know where it is. I am not aware of any problems involving this file that produced the symptoms you describe. Let's cross our fingers and hope you haven't found the first one.

Just on a hunch, try running the 260SP as the administrator on the first run. That might allow the 260SP to make some initial settings that it needs. Thereafter, you should be able to run normally.
Jim Henry

Post Reply

Who is online

Users browsing this forum: No registered users and 0 guests