This one was quite strange - the PPJoy installer would work when using the debug build of the DLL that registers the driver; when I used the release build the installer would fail to register the driver. Oh joy.
So then out comes windbg. Man's best friend for sure. As it turns out, there is one function in my DLL that requires a MULTI_SZ format string. Basically this means the string must end with two zero bytes; and the code was initialising it with only one zero, hence it failed. So why did the debug version work? I am speculating that the debug version includes extra variables that changes the packing in memory and the empty spots are probably filled with zeros... These zeros would make up for the one I forgot to add at the end of the string.
I really, really hope I don't other similar bugs lurking in there somewhere!!! The scary thing is that these bugs can lie dormant for years, just waiting for an innocent code change.
Subscribe to:
Post Comments (Atom)
do you have any idea when you are going to release a ppjoy for windows vista 64 bits?
ReplyDeletei have waited for a very long time, i realy hope you finish it, i would be very gratefull.
PPjoy for vistax86? I can't seem to get past the "copying JR_PPM.dll" stage of the installation!
ReplyDeleteGlad to hear that development for PPJoy is continuing. I would love some support for 64bit. Good luck.
ReplyDeleteI too would appreciate 64 bit drivers, I hope you're still working on this, it's been a while.
ReplyDeleteI'm pleased to see this is still going. It was sheer co-incidence I stumbled on this blog.
ReplyDeleteAnyway, this had made me feel like digging up my old C64 joystick and having a go on WinVice.
Much appreciated.
Ah well, last update in february... I guess your 64bits PPJoy is never going to be released... Too bad.
ReplyDeleteIncredible to see all the posts everywhere on the net, of people drooling to see you release it.
Hi Deon,
ReplyDeleteMy Name is Danny and I’m the programmer of WeeWheel http://www.weewheel.com, 1stly I want to thank you of the amazing work you did! Unfortunately the project has been stopped :(
If you need some help, I would like to help you if I can of course :P
Support for x64 Windows 7 would totally fulfill my dream of using the PSP as a gamepad on the PC. If you don't work on PPJoy anymore, please let someone else finish your project. I'd suggest Danny from weewheel.com =)
ReplyDeleteThis comment has been removed by the author.
ReplyDeleteI just wanted to say thanks for putting PPJoy out there, and, if it's any encouragement to development, I'd certainly be a paying customer for a future x64 Win7 release.
ReplyDeleteI hope this is still in work. There hasn't been any updates in a while. As far as support goes, I was thinking that the current PPJOY is plastered all over the web. Maybe just make a vista/win7 driver with 64 bit support and forget about backward compatability. Hope to hear an update soon. Not sure how I stumbled across this blog, but I hate the thought of moving back to a 32bit operating system to use this great tool.
ReplyDeleteI wanna 64 bit support
ReplyDeleteHi Deon,
ReplyDeleteas programmer and user of PPJoy I'd really like to help you to make a 64bit version of your great driver. Needless to say how many people use 64bit windows nowadays; it's a pity PPJoy lacks this support.
I'd also like to know if you have considered to make PPJoy open-source. You'd get free-hosting, free download servers and free help :) for development at Sourceforge.net... ;)
If you are interested and want some help, please let me know at francesco DOT montorsi AT gmail DOT com.
Thanks!
Francesco
You are right on the point that how debug version work that the debug version includes extra variables that changes the packing in memory and the empty spots are probably filled with zeros and these zeros would make up the last 2 zeros required.
ReplyDeletee-sign act
I really, really hope I don't other similar bugs lurking in there somewhere!!! The scary thing is that these bugs can lie dormant for years, just waiting for an innocent code change. bond touch germany , bond touch usa
ReplyDeleteIf you’re running your business on Microsoft Dynamics AX 2009 or 2012, you are no doubt aware that both software products are approaching the end of their life-cycles. Microsoft is ending Mainstream Support for Dynamics AX 2009, Dynamics AX 2012, and AX 2012 R2 this year and for AX 2012 R3 in 2021. That means no more security updates, hotfixes, warranty claims, design changes, features requests, and self-service support. You can purchase extended support. But be aware that extended support for AX 2009, AX 2012, and AX 2012 R2 ends in 2021. For AX 2012 R3, it will be available until 2023.
ReplyDeleteIf your business is thinking of upgrading from AX2012 to the latest Dynamics 365version, we recommend a complimentary Dynamics 365 upgrade assessment and cloud migration estimate. With the continuous releases we are seeing from Microsoft, this could be your last upgrade. The complimentary Microsoft Dynamics AX upgrade assessment Nevas Technologies offers to users has helped other businesses tackle obstacles.