|
View previous topic :: View next topic
|
| Author |
Message |
Sean Baggaley
Guest
|
 Posted: Fri Aug 06, 2004 3:27 pm Post subject: BSOD with MIDIoverLAN-CP
|
 |
|
Hi folks,
I just bought this as I have my keyboard and percussion machine connected to one PC, but would like to run the intense stuff (like RealGuitar!) on my newer PC, which has more RAM and speed.
MIDIoverLAN-CP installed perfectly on the new PC, but on the older PC (a Shuttle SS51G, original revision with a P4 1.8GHz and 512Mb RAM, running WinXP), it gives me regular BSODs and fails to work at all, even though it (sometimes) appears in SONAR 3.1.1.
The Blue Screen error mentions "TDI.SYS" before going away and rebooting the PC. (According to Google, TDI.SYS is an integral part of Windows XP's networking. I don't know if this is a coincidence though.)
I'd _really_ love to get this working as my only alternative is to buy yet another overcomplicated sound card with loads of stuff I don't actually want, just so I can have a couple of MIDI ports.
Oh well. I'll keep trying. There's a lot of crud on this PC, so it might just be "Windows Fatigue".
--
Sean Timarco Baggaley |
|
| Back to top |
|
|
Sean Baggaley
Guest
|
|
Posted: Fri Aug 06, 2004 6:53 pm Post subject: Odd...
|
|
|
It's fixed itself and the problem has gone away. It works well, although I agree with some of the others here and would like to see an alternative to running Sonar 3 just to loop the MIDI In to MIDIoverLan's driver.
Maybe a "Send MIDI Channels [X] through [Y] from [DRIVER] to LAN" section is called for.
My PC is now staring at me with an innocent expression on its desktop, as if to say, "What, me? Crash? Never! You must have imagined it. Both times."
I'm going to get my chainsaw and give it a "debugging" it'll never forget...
--
Sean Timarco Baggaley. |
|
| Back to top |
|
|
MOL_Moderator
Joined: 20 Jun 2003
Posts: 103
|
|
Posted: Wed Aug 11, 2004 7:12 am Post subject: Re: BSOD with MIDIoverLAN-CP
|
|
|
| Sean Baggaley wrote: | | ... The Blue Screen error mentions "TDI.SYS" before going away and rebooting the PC. (According to Google, TDI.SYS is an integral part of Windows XP's networking. I don't know if this is a coincidence though.)... |
Yes, TDI.SYS (Transport Driver Interface) is part of WXP. Probably this copy of Windows is not stable (some modules are corrupted).
1. Try to use some MOL CP port (all others must be disabled) in local mode as LocPipe; it won't use network drivers.
2. Try to repair/reinstall this WXP copy. |
|
| Back to top |
|
|
|
|
