QUOTE (Grilf @ Sep 9 2004, 12:23 PM) |
Have you tried to uninstall, and then reinstall? |
I have tried everything coneivable, including uninstalling x-control and the usb driver and hand pruning my registry.
did u try and use it b4 u installed the sp2?
Delevopers should take a look at http://www.MS.com/te...n/sp2mempr.mspx
and give extra attention to
"Applications that attempt to violate DEP will receive an exception with status code STATUS_ACCESS_VIOLATION (0xC0000005). If an application requires executable memory, it must explicitly set this attribute on the appropriate memory by specifying PAGE_EXECUTE, PAGE_EXECUTE_READ, PAGE_EXECUTE_READWRITE or PAGE_EXECUTE_WRITECOPY in the memory protection argument of the Virtual* memory allocation functions. Heap allocations using the malloc() and HeapAlloc() functions are non-executable."
I have also be playing around with compatability Administrator3.0 from MS trying to get X-Control to work...Still trying..
Tokyoturnip.
Hmmm....Somehow the link got screwed up...
http://www.MS.com/te...n/sp2mempr.mspx
Should go to m i c r o s o f t .com but the got changed to www.ms.com somehow..Weird.
MS SP2 changes
There we go, I think I posted the link right this time.
QUOTE ([email protected] @ Sep 9 2004, 09:39 PM) |
did u try and use it b4 u installed the sp2? |
Yes, and it worked fine for weeks before SP2 was installed.
tokyoturnip,
Good stuff. You are linking to morgan stanley, however, not
microsoft.com. I think the board software is doing something screwy with the link.
http:
//www.microsoft.com/technet/prodtechnol/winxppro/maintain/sp2mempr.mspx
So does it work if you toggle the DEP settings for the application?
QUOTE |
For the purposes of application compatibility when DEP is set to the OptOut policy level, it is possible to selectively disable DEP for individual 32-bit applications.
For end users, the Data Execution Prevention tab in System Properties can be used to selectively disable DEP for an application.
|
I am very curious since this is one of the issues that is actually keeping me from doing the SP2 upgrade
It doesn't work if I toggle DEP for the app or system wide. Same error.
Same here about no success on disabling DEP on app or system.
I disabled on system by setting /noexcute=AlwaysOff however still did not do it.
I think I read somewhere on MS that the kernal is protected no matter what.
Using a dependency walker i can that X-control trys to hook into some of the system files, which I am sure SP2 does not like...
Will be flashing my chip from a W2K box for now.
tokyoturnip.
i have SP2 installed on XP. Used X-control software with no problems.
NghtShd, me and you just have bad luck. SOL.
invincible did you install X-control before you upgraded?
I installed SP2, before I attempted to install X-Control.
How about you NghtShd? Before or after?
Also, Easy released the recent USB driver upgrade which I installed but did not help.
Which I did not think would help because it only used when you connect up the USB cable..
tokyoturnip
I installed it before SP2. I wonder if the people who can run it under SP2 have systems which don't support DEP in hardware.
Have any of you people check with your Motherbaord manufacturer for updated USB drivers for SP2?
As reproduction of this error is impossible, as some clean system clean and reinstall everything and it works.....but no know exact way to reproduce issue.
Yes, my drivers are up to date and all my USB stuff works as it did before SP2 except x-control and x-serial.
It's a shame, because after the latest x-chip OS update I was able to get the x-serial debug output working (my main reason for using this chip) and now it's useless unless I go back to pre SP2.
Both of my systems are using AMD processors, BTW. Have you tested with AMD or only Intel?
I've tested with intel 2.8 and 2.2 processors and a AMD 2000 and 2800+'s.
Did you chekc device manager after connecting X-Chip and verify that the driver and device are successfully detected? It could be the .exe and not drivers that are issues.
QUOTE (cravavr3 @ Sep 29 2004, 03:40 PM) |
I've tested with intel 2.8 and 2.2 processors and a AMD 2000 and 2800+'s.
Did you chekc device manager after connecting X-Chip and verify that the driver and device are successfully detected? It could be the .exe and not drivers that are issues. |
Yeah, I assumed that it was the exe since thats what crashes, though it could be driver related. The driver shows up in device manager as installed and working properly, for what that's worth.
If the driver is showing up successful, we can assume its an issue with the .exe file. But like you state coudl be driver related.
But......very strangly is sysmptom cannot be duplicated.........just happens to some and others not.
I think the best solution is to start a Database of issue of XP SP2.
Example(s):
My PC loaded with SP1, had xcontrol installed, donwlaaded the 256 install file of SP2 and installed and xcontrol works.
My PC loaded with SP1, did not have xcontrol installed, let windows update automatically install SP2, then tried loading xcontrol and doe snot work famouse 0x00000005 error.
They need to find common way of reproducing issue, once that maybe they can track down problem 100% with SP2.
I have been contacted by the Team X-Chip to beta test a possible SP2 ( 0xC00000005 ) error fix. Since I do not have the issue, I have been instructed to forward the file to a few individuals to test who are encountering the ( 0xc000005 ) with SP2 installed issue.
Please PM me your email address and I will email file ASAP. I am limiting this to the 1st 5-10 PM's. As I do not have alot of time to send files out as this is a Beta and may or may not fix issue, if it doesn't it may or may not become a public file, if it does, some tweaks maybe make and a mor eofficial release will follow.
Same error as before.
May be relavent and I'm not sure if I mentioned this before, but the error dialog happens twice when I launch either x-control or x-serial. I get the error dialog, click the OK button, and then a second dialog pops up.
I have tested the betafile that cravar3 sent me. Sorry to say it did not solve the problem. Still get the 0xC00000005 error. Maybe others will have luck.
tokyoturnip
I had the same exact problem until I just found a solution. What you do is go to the add/remove menu from control panel, and remove the service pack 2 update. After I did that the x-control app started working perfectly.
QUOTE (kasserole @ Oct 7 2004, 12:06 AM) |
I had the same exact problem until I just found a solution. What you do is go to the add/remove menu from control panel, and remove the service pack 2 update. After I did that the x-control app started working perfectly. |
LOL. No kidding? Removing SP2 fixes the SP2 problem? Whodathunkit!
Unfortunity the file did not work with SP2 issues.
It was well documented and posted that SP2 on these machines that have issues if removed worked.
From my understanding on what I was told, was the test file meet all the SP2 criteria for DEP, etc.
So must be another issue then the .exe
QUOTE (kasserole @ Oct 7 2004, 01:16 AM) |
I woulda never thought it'd be that simple, but hey |
Um, I thought you were joking. Of course removing SP2 will fix the SP2 problem, because it is caused by a conflict between some component of the x-chip software and SP2.
NghtShd: Have you tried the beta drivers i emailed you this morning?
You must of not selected Have Disk as I stated in email.
Oh well... I will pass the info along.
But can you provide some info on your system:
USB 1.1 or 2.0 ports?
Video Card?
Sound Card?
Any conflicting drivers in device manager?
nghtshd: Take a look in the registry HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Enum\USB
How many entries do you have with vid_0547 ?
QUOTE |
How many entries do you have with vid_0547 ? |
Two.
Vid_0547&Pid_1002
Vid_0547&Pid_2131
Ok nghtshd, just wanted to compare to my setup (which works fine with SP2)
I also only have those two entries, so guess it is not due to any conflicts with other Cypress devices.
Question about people taking SP2 update and have issue?
Did they do through MS Update or download 256MB file?If download is it from a reliable source???
Are you using winXp home or winxp pro?
Are you using a legit key or one from internet?
Did you need to change key to let SP2 load?
Did you have X-Control working prior to SP2 update installed? Basically was it installed prior to SP2 install.
These questions probable won't help much, but by narrowing down SP2 to see where issue lies may becoem usefull.
Tried the new dll file cravavr3 sent me. Unfortunately no go. The dll file itself appears to have same mod date as the Ezusb.dll, however the inf file to install it is smaller.
Information regarding my SP2 install.
1. Used the 256Mb network install upgraded from SP1.
2. Using Home at Home and Pro at work (did not work on both).
3. Home using a legit key, OEM. At work corporate addition so no activation.
4. Did not do any key changes to install.
5. Did not install x-control before install SP2
More information. Had to uninstall SP2 at work because they said they do not support it...and X-control works of course...did not work with SP2 installed, but work with it uninstalled.
Machine at home is an emachines T1842 (if you want to get machines specs) the motherboard is intel 845GL with celeron 1.8ghz CPU, onboard graphics.
Machine at work Dell optiplex GX110 (don't know specs, but beleive it is intel chip).
tokyoturnip
After doing some more testing, I am pretty sure that this error has nothing to do with DEP.
I have tried several SP2 installations without any problems, and DEP was enabled on all of them.
I just read the first post from Tokyoturnip again, and he states that the error msg he receives is:
"The application failed to initialize properly (0xc0000005). Click OK to terminate the application." It creates a entry in the system eventlog, and sending the info to MS online debug says that it can not access a needed dll or file
Have you checked that the required dll file is in the same dir as x-control?
Try copying the dll to \windows\system32\
Do you have any other devices that uses a dll file with the same name (xusb.dll)? Try searching your harddrives for a dll file named the same.
I don't see any reference to the dll file in my event log or the error.
Just this log entry (twice for each time I try to launch the app):
"Application popup: X-Control.exe - Application Error : The application failed to initialize properly (0xc0000005). Click on OK to terminate the application."
If I remove the dll I get:
"Application popup: X-Control.exe - Unable To Locate Component : This application has failed to start because XUSB.DLL was not found. Re-installing the application may fix this problem."
Proud to anounce the 1.05 version of X-control that Cra Vavr3 sent me today appears to be working. Looks like I am still using the ezusb.dll driver, however I can read from the chip. (Have not tried to write to yet...Scared..LOL).
No application errors and able to run as a XP home admin and limited user.
I hope it works for others.
tokyoturnip