Post by: tokyoturnip on August 28, 2004, 04:05:00 PM
I was able to install it and run it on a friends Win2000 machine and run with out problems...However I can not impose on my freind everytime I want to flash the BIOS.
I want to make sure that I flash it with the 1.6bios before putting it in my Xbox. Is the Evox 1.6 BIOS already installed by default.
Any help appreciated.
Post by: christineyoung on August 28, 2004, 06:13:00 PM
You have names wrong....
Evox 1.0 is X-Chips secret Bios, contains two files full.bin and full16.bin, the full16.bin is for 1.6 xbox's only and the full.bin is for 1.0 to 1.5 xbox's.
The defaulted shipping image on X-Chip is legal Cromwell so no unsigned code access so you will need to load a proper bios to play unsigned code.
As for SP2 and XP, I have Home and Pro installs with and without SP2 and have not run into any issues with drivers, I would 1st connect X-Chip to PC then goto system/ hardware preferences and see if anything conflicting.
Also, in X-Control on your PC does the X turn green top left when connected also is legacy 1.1 support enabled in bios if you have 2.0 ports?
Post by: tokyoturnip on August 28, 2004, 08:18:00 PM
No problems or conflicts with drivers. At OS level, OS see the chip attached.
I can not even open X-control, which is why I posted. I get the error as stated before when I click to open X-control on the exe itself, or from the start menu.
With the Chip hooked up, or not hooked up i still get same error, and X-control does not open. I never get to see the GUI.
I even tried W2k, 98, NT compatablity mode, but no success.
I found two MS KB articles regarding DEP (data execution protection) KB 878474 and KB 875352, however following the instructions on disabling DEP, does not change my situation.
I have a 1.6 Xbox, will I be able to put in the chip without flashing the bios first, and it should boot to Cromwell without frying my system? Once chip is in and I if I did not flash with correct BIOS Should I be careful of pressing any buttons during boot up? Don't want to activate any of the secret BIOS that are not designed for my system, and have a doorstop.
I will check on the 1.1 Legacy port option in BIOS. I beleive it is enable since I know I have some non 2.0 USB things connected.
Thanks for the reply Christine.
Post by: christineyoung on August 28, 2004, 10:01:00 PM
Use the file full16.bin when you find evox 1.0 download( xbins has it ). You will need working X-Control to write the 4MB image can't do it through CDRW or DVD-R. But once you have it working just do a File - Load Raw and select your 4 MB full16.bin file and then do a X-Chip - Write Changes.
After reading your initail post i did a few searches on the error code you reported and majority of issues was not updated firmware on devices, but since X-Chip only has one driver release cannot be it, possible bad download and install but not likely.
Do you have updated drivers for your USB ports? And all devices on your PC?
When you connect X-Chip what does it list in the Device Manager as connected USB devices?
Post by: [email protected] on August 29, 2004, 06:29:00 PM
Post by: tokyoturnip on September 01, 2004, 07:04:00 PM
Sorry to admit, I took the easy way out and just installed W2K on a piece of junk old machine, just enough to run X-control to flash the chip once. Was able to flash it using W2K without problems. Then I had fun trying to burn a Evox boot disk 10 different ways, until I learned about the X-Box compatable checkbox in NERO, then I was off and running.
If you know the solution for the problem I had, feel free to post it to share with all, I am sure others with same problem, and only access to a WinXP machine would like to know.
Post by: [email protected] on September 01, 2004, 10:14:00 PM
anyway the solution i used was simple.
i just did alll the updates for winxp
ie..... WINDOWS UPDATE!!
its a like a dll. error type deal..
and what version of nero are u using? lol i didnt know about the xbox thing...
Post by: tokyoturnip on September 02, 2004, 06:45:00 PM
Hmm, I thought I am all up-to-date using Windows Update. But I think SP2 is a lot more restrictive and causing problems..
Any how, I use NERO 6. The Xbox compatablity check box is when you burn CD ISO/UDF type, there is a checkbox on one of the tabs. I forget, I am at work. But the key is CD ISO/UDF type will make the Xbox compatablity checkbox available.
Post by: [email protected] on September 02, 2004, 11:03:00 PM
yeah i understand what u mean but i am running xp now and the only thing i did when i got that damn error was... lol updates... thats it.... so im pretty convinced it was posaibly that...
Post by: NghtShd on September 06, 2004, 07:42:00 PM
Error: The application failed to initialize properly (0xc0000005).
I've accepted all the updates available. I get the same error on both my desktop PC and my laptop.
Post by: tokyoturnip on September 07, 2004, 06:29:00 PM
Well at least I am no longer alone with this problem. Just proves I am not crazy, and more reason for developers to try to get it to work with XP SP2, or at least clue us in on setting changes we can make to get it to work, as more and more people will install SP2.
Tokyoturnip
Post by: [email protected] on September 07, 2004, 07:32:00 PM
Did u follow EVERY step.... andi mean EVERYSTEP..
cuz it 2 times it will say pick the bottem of 2 selections... hard to explain. if u installed the wrong one... that could have done whats going on..
also..
goto goolge.com. and type in that error message..
and c what it says is the problem.
thats all i can think of..
cuz im running THE SAME os as u guys..
Post by: NghtShd on September 07, 2004, 08:06:00 PM
I think that error is an access violation. Like maybe a function returned a null pointer and somebody forgot to check that (just assumed that something would be there).
Post by: [email protected] on September 08, 2004, 10:26:00 PM
Post by: NghtShd on September 08, 2004, 11:02:00 PM
I uninstalled everything and I also went through the registry and cleaned out all x-chip related stuff left behind. Then I reinstalled x-control and the usb driver.
I read one report of a person successfully running x-control on sp2, but he installed it after sp2 was installed, so maybe that's why his worked.
Post by: Easybuy2000 on September 09, 2004, 07:24:00 AM
Post by: Grilf on September 09, 2004, 09:20:00 AM
Post by: NghtShd on September 09, 2004, 09:45:00 AM
| 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.
Post by: [email protected] on September 09, 2004, 06:36:00 PM
Post by: tokyoturnip on September 09, 2004, 08:56:00 PM
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.
Post by: tokyoturnip on September 09, 2004, 08:58:00 PM
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.
Post by: tokyoturnip on September 09, 2004, 09:00:00 PM
There we go, I think I posted the link right this time.
Post by: NghtShd on September 09, 2004, 09:36:00 PM
| 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
Post by: Grilf on September 09, 2004, 09:49:00 PM
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
Post by: NghtShd on September 09, 2004, 11:21:00 PM
Post by: tokyoturnip on September 10, 2004, 10:10:00 PM
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.
Post by: invincible on September 11, 2004, 09:43:00 AM
Post by: tokyoturnip on September 11, 2004, 02:29:00 PM
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
Post by: NghtShd on September 11, 2004, 03:37:00 PM
Post by: cravavr3 on September 29, 2004, 09:41:00 AM
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.
Post by: NghtShd on September 29, 2004, 12:34:00 PM
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?
Post by: cravavr3 on September 29, 2004, 12:37:00 PM
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.
Post by: NghtShd on September 29, 2004, 07:53:00 PM
| 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.
Post by: cravavr3 on September 30, 2004, 07:19:00 AM
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.
Post by: cravavr3 on October 05, 2004, 09:46:00 AM
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.
Post by: NghtShd on October 06, 2004, 04:38:00 PM
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.
Post by: tokyoturnip on October 06, 2004, 08:59:00 PM
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
Post by: kasserole on October 06, 2004, 09:03:00 PM
Post by: NghtShd on October 06, 2004, 09:26:00 PM
| 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!
Post by: kasserole on October 06, 2004, 10:13:00 PM
Post by: cravavr3 on October 07, 2004, 07:04:00 AM
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
Post by: NghtShd on October 07, 2004, 07:20:00 AM
| 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.
Post by: cravavr3 on October 07, 2004, 11:04:00 AM
Post by: cravavr3 on October 07, 2004, 12:49:00 PM
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?
Post by: Grilf on October 07, 2004, 12:56:00 PM
How many entries do you have with vid_0547 ?
Post by: NghtShd on October 07, 2004, 01:10:00 PM
| QUOTE |
| How many entries do you have with vid_0547 ? |
Two.
Vid_0547&Pid_1002
Vid_0547&Pid_2131
Post by: Grilf on October 07, 2004, 01:18:00 PM
I also only have those two entries, so guess it is not due to any conflicts with other Cypress devices.
Post by: cravavr3 on October 07, 2004, 01:36:00 PM
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.
Post by: tokyoturnip on October 08, 2004, 06:09:00 AM
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
Post by: Grilf on October 10, 2004, 07:48:00 AM
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.
Post by: NghtShd on October 10, 2004, 09:19:00 AM
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."
Post by: tokyoturnip on October 12, 2004, 07:02:00 PM
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