Could someone please help me with the older model of MIDI express XT, the one without the USB, only parallel port. The preoblem is that I cannot install the drivers for the port under Win XP. The ones that I downloaded from the MOTU sites are in valid, and also this model is not listed anymore ( !!!! like it is not their product anymore!!!!)
Thanks!
MOTU MIDI express XT
Moderator: James Steele
Forum rules
Discussion related to installation, configuration and use of MOTU hardware such as MIDI interfaces, audio interfaces, etc. with Windows
Discussion related to installation, configuration and use of MOTU hardware such as MIDI interfaces, audio interfaces, etc. with Windows
It works.
It is vital that You carefully follow the procedure described in the .htm document named "read me first!", provided with the driver. Follow the instructions step by step. Of course firstly remove any traces of previous installations.
Then, while powering the PC up, make sure the MEXT is in user preset mode (green light on), otherwise it will most probably be recognized as some Flyer ports.... useless at its most. I don't use the factory preset mode at all and the equipment is recognized properly.
Then run Clockworks software, it should indicate MIDI Express XT installed. DON'T try to add any "DTP", though the software suggests this may be an option. If Clockworks crash, it means your equipment is not working ok, or the drivers weren't installed properly. If Clockworks does not crash, but there's nothing in the small window, run the "LPT Refresh" utility (after making sure the user preset mode is on) and it will detect the hardware without restarting even if it was not detected during Windows boot - up.
all the best
It is vital that You carefully follow the procedure described in the .htm document named "read me first!", provided with the driver. Follow the instructions step by step. Of course firstly remove any traces of previous installations.
Then, while powering the PC up, make sure the MEXT is in user preset mode (green light on), otherwise it will most probably be recognized as some Flyer ports.... useless at its most. I don't use the factory preset mode at all and the equipment is recognized properly.
Then run Clockworks software, it should indicate MIDI Express XT installed. DON'T try to add any "DTP", though the software suggests this may be an option. If Clockworks crash, it means your equipment is not working ok, or the drivers weren't installed properly. If Clockworks does not crash, but there's nothing in the small window, run the "LPT Refresh" utility (after making sure the user preset mode is on) and it will detect the hardware without restarting even if it was not detected during Windows boot - up.
all the best
Ludi Cure,
I did way too much research on that several months back after experiencing the exact same problems you're having. I finally gave up and wish that I hadn't wasted so much time or bought the thing in the first place.
While the previous post's workaround may occasionally work for some people, it seemed that it doesn't work 100% for most (no offense Retali8
). Also, even after a successful install, you can have trouble getting detections on bootup with or without the workaround, or worse yet have it disappear mid-session. It's possible that many systems are just not going to work with it, or that those who have been successful, just haven't said the "magic word" to make it disappear. It sucks because I've always trusted and preferred a solid com port connection for MIDI (my MIDI requirements are fairly modest these days).
BTW- It doesn't look like just one interface is affected by this type of thing. I posted a link a while back to some very detailed, yet older, workaround instructions for the MOTU com interfaces (should show on a search). I've been lucky with my PCI424/2408mk3, but there are a bunch of PC'ers complaining of similar detection failures with their audio hardware and USB MIDI hardware. Doesn't look like they're "overstaffed" in the 2K/XP department.
Good Luck
-George
PS- I went FTP diving and came back with a whole folder of MIDI drivers during my battle with the MOTU, all the way up to the "current" 2.51 unified bundle from 2004. They all behaved the same way. If you ever happen to have a 98SE rig running MIDI, it did seem to install and detect well on one here (not much use for me either).
I did way too much research on that several months back after experiencing the exact same problems you're having. I finally gave up and wish that I hadn't wasted so much time or bought the thing in the first place.
While the previous post's workaround may occasionally work for some people, it seemed that it doesn't work 100% for most (no offense Retali8
). Also, even after a successful install, you can have trouble getting detections on bootup with or without the workaround, or worse yet have it disappear mid-session. It's possible that many systems are just not going to work with it, or that those who have been successful, just haven't said the "magic word" to make it disappear. It sucks because I've always trusted and preferred a solid com port connection for MIDI (my MIDI requirements are fairly modest these days). BTW- It doesn't look like just one interface is affected by this type of thing. I posted a link a while back to some very detailed, yet older, workaround instructions for the MOTU com interfaces (should show on a search). I've been lucky with my PCI424/2408mk3, but there are a bunch of PC'ers complaining of similar detection failures with their audio hardware and USB MIDI hardware. Doesn't look like they're "overstaffed" in the 2K/XP department.
Good Luck
-George
PS- I went FTP diving and came back with a whole folder of MIDI drivers during my battle with the MOTU, all the way up to the "current" 2.51 unified bundle from 2004. They all behaved the same way. If you ever happen to have a 98SE rig running MIDI, it did seem to install and detect well on one here (not much use for me either).
I'm running the same interface under XP with no problems. Ocassionally, it won't be recognized at boot up. But LPT refresh and it works. I have a mate that also uses this. His system does not always refresh and when it does, he has to leave Clockworks running. The only difference in our systems is his has SP2 (XP). I haven't installed SP2 because my studio machines never touch the internet.
Now all I have to do is get it working on a dual G4 under OS9/OSX.
T
Now all I have to do is get it working on a dual G4 under OS9/OSX.
T
Seems WinXP Service Pack 2 is the engine of trouble then, because I'm also running SP1, and everything is fine with the MEXT. I'm using the unit extensively for several hours a day and never needed to keep Clockworks open.
If that's any help: I use the MOTU with Logic Audio Platinum PC (last version for PC) on Windows XP SP!, EgoSys Waveterminal 2496 audio interface, hardware system is ECS K7S6A mobo (on SiS chipset, which I consider best for audio) and Athlon XP 1800.
all the best
If that's any help: I use the MOTU with Logic Audio Platinum PC (last version for PC) on Windows XP SP!, EgoSys Waveterminal 2496 audio interface, hardware system is ECS K7S6A mobo (on SiS chipset, which I consider best for audio) and Athlon XP 1800.
all the best
I'm just on SP1 myself, and couldn't get the MicroExp. to work consistently here, so it may be hardware dependent too, but there were enough similar reports with the com port boxes that it's hard to believe they couldn't have had at least one problematic test rig to examine at MOTU. I don't feel that the refresh utility, or the clockworks thing are acceptable solutions in 2005, and neither worked here anyway. I tried all the different port settings in the bios as well as in XP. This was on an ASUS A7N8X-E/AthlonXP2500.
Retali8- I'm coincidentally on an ECS K7S5A/AthlonXP1800 right now. I may bring the MOTU home just to check it out. It would do even less good here than on the secondary 98 rig at the studio, but it would be fun to at least see how it was intended to perform.
George
Retali8- I'm coincidentally on an ECS K7S5A/AthlonXP1800 right now. I may bring the MOTU home just to check it out. It would do even less good here than on the secondary 98 rig at the studio, but it would be fun to at least see how it was intended to perform.
George
-
scottperkins1
- Posts: 2
- Joined: Fri Dec 23, 2005 5:10 am
- Primary DAW OS: Unspecified
MIDI express xt with usb will not install
while running the install cd I get the following message.
c\:windows\system32\autoexec.nt. The system file is not suitable for running MS-Dos and microsoft windows applications.
c\:windows\system32\autoexec.nt. The system file is not suitable for running MS-Dos and microsoft windows applications.
Scott Perkins
-
scottperkins1
- Posts: 2
- Joined: Fri Dec 23, 2005 5:10 am
- Primary DAW OS: Unspecified
more on the previous post
I hit enter a little early but my question is if anyone else has had this problem and if there is a solution. Tech support at motu told me to contact microsoft and you guessed it, they told me to contact motu.
any help is appreciated.
any help is appreciated.
Scott Perkins
Re: MIDI express xt with usb will not install
Don't run the install cd then. Just download the drivers from the MOTU site, use the driver installer and follow the instructions.scottperkins1 wrote:while running the install cd I get the following message.
c\:windows\system32\autoexec.nt. The system file is not suitable for running MS-Dos and microsoft windows applications.
best
Don't know exactly if that makes any real difference, but I'm speaking of MOTU MIDI Express XT interface, not Micro Express...Jidis wrote:I'm just on SP1 myself, and couldn't get the MicroExp. to work consistently here
I think Refresh utility is ultraimportant, 1st, if you're having probs with device recognition at system bootup, 2nd, if you turn the MEXT on while having the PC already on. So there's no true need to boot up Windows with the interface turned on. Clockworks is also vital, it's an editor. Kinda like MIDI-OX.Jidis wrote: I don't feel that the refresh utility, or the clockworks thing are acceptable solutions in 2005, and neither worked here anyway.
Both work ok here (and I guess should work anywhere granting the installation was properly done, but that really might be system dependant so I'm not stating this as a fact).
Best wishes with Your efforts. As I said, it should generally work. On my system about once a month or so the device does not start up properly , but then the refresh does the reviving job. That's the only problem I have with the unit, and I don't complain much, since I got it for about 50$Jidis wrote:I tried all the different port settings in the bios as well as in XP. This was on an ASUS A7N8X-E/AthlonXP2500.
Retali8- I'm coincidentally on an ECS K7S5A/AthlonXP1800 right now. I may bring the MOTU home just to check it out. It would do even less good here than on the secondary 98 rig at the studio, but it would be fun to at least see how it was intended to perform.
George
all the best