Nistune locking up Vista laptop

Matt · Post by **Matt** » Sun May 18, 2008 6:06 pm

thanks for those answers. you might not know these ones, just trying to round things down

the blazt cable which uses different drivers to what I have here

and might be part of the reason for the whole system freeze up. might have to purchase one of these to get through this. perhaps it shouldnt matter since its a standard serial port device which is why no special drivers

but may be why you are getting the crash and others arent with vista (most others would be using PLMS consult FTDI drivers only without the emulator usage)

does the crash occur with just wideband enabled?

does the crash occur with just consult enabled and streaming?

what about when romulator is not used?

thanks
matt

Matt · Post by **Matt** » Mon May 19, 2008 1:44 am

Also ordered a blazt cable so I have the same piece of hardware. I dont have an innovate, but I'll see how it goes with a different w/b unit

JasonKemmerer · Post by **JasonKemmerer** » Mon May 19, 2008 6:40 am

Matt wrote:thanks for those answers. you might not know these ones, just trying to round things down

the blazt cable which uses different drivers to what I have here and might be part of the reason for the whole system freeze up. might have to purchase one of these to get through this. perhaps it shouldnt matter since its a standard serial port device which is why no special drivers

but may be why you are getting the crash and others arent with vista (most others would be using PLMS consult FTDI drivers only without the emulator usage)

does the crash occur with just wideband enabled? not sure, when its crashed both the consult and wideband are on.

does the crash occur with just consult enabled and streaming? it has but maybe once since I have all the gizmos running

what about when romulator is not used? will need to try that. I usually turn on the emulator first, the consult 2nd and last the wideband.

thanks
matt

thank you!

JasonKemmerer · Post by **JasonKemmerer** » Mon May 19, 2008 1:31 pm

I was able to play with the latest version .9254 today. I had compatibility running for Win200 and it would crash just going to Configuration and browsing the folders to select the Innovate directory for the wideband data.

I switched compatibility to XP SP2 and that issue went away. I have some uploaded jpegs of what it brought up.

Once I fixed this issue I had trouble getting the correct COM port in the configuration menu for the wideband. I had to manually switch the com port in device manager so NIStune could see the port. (Drop down menu in NIStune config menu wouldn't allow me to choose the right port).

Got it all running on the Moates Ostrich 2.0, Blazt USB cable, and Innovate W\B. Had it running for about 10 minutes with no crashes! I would have spent more time but it is about 103 degrees Fahrenheit over here.

I could connect and disconnect without any problems. I will have the opportunity to see if there is an issue with the romulator on Friday. The Ostrich 2.0 is on my personal zed. I use the romulator on customer's cars.

Matt · Post by **Matt** » Mon May 19, 2008 10:14 pm

From what I have worked out... if you have a crash on a particular port it will no longer be able to access that port

Two ways around this are reboot or chance the COM port of the device. I have seen it a few times lately. Trying to repeat

Ran Win2000 compatibility mode and connected to DLP and PLMS USB consult no problems. No problems with browsing either for wideband folder. I cant seem to make the crashes happen. This is a new PC with just vista installed

JasonKemmerer · Post by **JasonKemmerer** » Tue May 20, 2008 10:27 am

Very strange, when running 2000 compatibility it would crash like clock work.

My system is fresh, just bought this laptop 2 weeks ago too.

However it seemed pretty happy with XP SP2 compatibility.

Matt · Post by **Matt** » Tue May 20, 2008 1:41 pm

Maybe I'll try the same Vista version as what you are using

Also I'm not using the Innovate unit. I might purchase a LC-1 just to test this out and use on my car since I'm just using PLs techedge at the moment.

LC-1 are about $200USD

JasonKemmerer · Post by **JasonKemmerer** » Sun May 25, 2008 5:27 pm

So used it on Friday and was having problems still

To keep it from completely locking up right after I get some Wideband input tracer logged I shut down the consult logging. I quickly tune the maps and shutdown the wideband logging. This is the only way otherwise it will look up just sitting their logging with all three one (emulator, wideband, consult).
I can have the emulator on all the time with no problem.

Program was acting funny to after crashing, Vista was finding drivers for a serial mouse and my cursor was moving around on its own!

Shut it down completely and it was fine. Basically just shutting it down from the lock up and starting it up would not be enough. I would have to shutdown again just to have Vista and Nistune act correctly.

Matt · Post by **Matt** » Sun May 25, 2008 8:47 pm

Blazt cable arrived on Friday and waiting for the Innovate LC1 to arrive

There is something really strange going on with the drivers then. NIStune simply treats these as serial ports and communicates with them

As long as the calls to the API functions which work with the drivers are legitimate from the NIStune end then things should work fine (as has been the case so far with Win98/XP usage).

However if there is a driver issue (manufacturer of device) or driver compatibility issue (Vista driver problem or incompatibility) then this might be outside my scope of control.... apart from the fact that if other software (eg using NissanDataScan and LogWorks) is working okay not causing any crashing then some of the API functions being called that interact with the driver may have an issue

Now it is either the Blazt driver or a problem with the Innovate unit feeding in. Are you using a USB-serial adaptor to get the Innovate data into your laptop?

If so what USB-serial adaptor are you using?

JasonKemmerer · Post by **JasonKemmerer** » Mon May 26, 2008 3:43 am

Yes, I am using the iogear serial to usb adpater for the Innovate. Using its own drivers that came with it.

Again, I never installed any drivers for the Blazt specifically. Using the drivers Windows found automatically.

Matt · Post by **Matt** » Mon May 26, 2008 1:50 pm

okay I found this IOGear GUC232A
http://www.iogear.com/product/GUC232A/
but can only be purchased in the US/Canada

Locally its about 18 days before stocks available

However the unit looks the same as my Aten one UC232A
http://www.aten.com/products/productIte ... 2316346005

I dont know if they are from the same manufacturer (could be) but I would like to look/try your drivers out on my unit under Vista if possible to see if its the same

I'm going to try the driver out on my unit and see how it goes

Matt · Post by **Matt** » Mon May 26, 2008 2:01 pm

Just downloaded the drivers for both units...

The XP and Vista IOGears ones both are commented as 'ATEN' and have the same vendor/product IDs

%DeviceDesc% = ComPort, USB\VID_0557&PID_2008
%DeviceDesc% = ComPort, USB\VID_067B&PID_2303

The IOGear has an 'extra' ID line for their unit (since they have different manufacturer name) but it means I can use your drivers with my device

JasonKemmerer · Post by **JasonKemmerer** » Mon May 26, 2008 4:06 pm

Yes you are right! The iogear is listed in device manager as ATEN.

Matt · Post by **Matt** » Mon May 26, 2008 6:12 pm

Okay I've done more searches on google. Are you getting a BSOD (Blue screen of death?). If so is it similar to reported below? I havent run this converter yet with Vista... but will soon!

http://www.adras.com/ser2pl-sys-DRIVER- ... 563-1.html
http://www.pcreview.co.uk/forums/thread-525084.php

Bluescreen problems
1.- DRIVER_IRQ_NOT_LESS_OR_EQUAL
On the bottom is text
- ser2pl.sys
2.Window has been shut down to prevend more damage ...
On the bottom is text
STOP:0x0000007B, C0XF993E640, 0XC0000034,
0X00000000,0X00000000

I have downloaded all the possible fix to my database
manager. But still i got these bluescreens

What version is your driver for Aten showing up as?

I also found
http://www.bridgemateftp.co.uk/faq/

Version 2.0.2.1 of the Aten USB-serial converter driver has been tested successfully on Microsoft Windows XP and Windows Vista. (as at April 2008)

The file which is suspect is ser2pl.sys which is a Prolific chipset serial driver used in various USB converters including Aten and IOGear

Another post similar to the above
http://www.vistaheads.com/forums/micros ... ution.html

Since my original posting I have done a lot of testing and found that ser2pl.sys version 2.0.2.1 seems to be the only workable solution both on XP and on Vista. The size of this version is 48640 bytes.

That last link goes to the Aten website with the rar file containing latest vista drivers. Let me know how you go with this. It might not fix the NIStune crash issue but will probably help the BSOD issue (if any) and I can continue chasing the crash issue using same drivers from this end.

My major issue is that I developed using Visual C++ 6.0 under XP to maintain speed and compatbility ... but this is not a supported (compatible) program for Vista. The end applications (ie NIStune) should be still but running under a debugger may not work...

Microsoft recommends (forces?) developers upgrade to Visual Studio 2005 (SP1) or 2008 which are compatible to both produce apps. However this then makes them require .NET which is not good for say older machines running Win98 (especially when we want to achieve higher speed logging and feedback over three com/four com ports at the same time)

See how we go from here anyway. Still waiting for the innovate to arrive

JasonKemmerer · Post by **JasonKemmerer** » Tue May 27, 2008 5:23 pm

No BSOD, just a cold dead freeze.

Looked in device manager and opened up com ports to see what driver it pulled up.

2.0.0.18 dated 7\16\2003 !!!!!

Could that be right?

Anyways downloaded: UC232A_v2021.exe

Tried to update driver but Windows says the one I already have is the most up to date. WTF?

So I manually deleted the old files and reinstalled with the new.