|
||||
Quote:
The method your PPC uses to talk to a Windows PC its connected to used to always be a serial connection emulated over USB. Beginning with WM5 MS moved to a networking-type connection called RNDIS. It had a ton of problems at first, made worse by the fact that you couldn't choose any other method. Around the time of AKU 2.0 of WM5 MS debuted the "USB to PC" applet in Settings->Connections to facilitate switching back to the serial driver if desired. Also, RNDIS has improved a lot compatibility-wise since it first debuted with WM5. However, on some systems it will still have problems (due to firewalls, corp lockdowns with group policy, etc.). In those cases reverting to the serial driver (unchecking the "use advanced networking" checkbox in Settings->Connections->USB to PC) is the usually the solution to the problem (and there's no downside, although I'm not positive if Internet Sharing works in that mode). |
|
||||
Thanks for the quick reply ...
So, anyway of diagnosing where the problems is? I've already tried turning anti-virus off, firewall off, etc ... no luck. Suprisingly, the most sure-fired way of getting my Vista pc to sync is to use bluetooth. The only problem with BT is Media Center doesn't recognize the SD card for sync'ing. Quote:
|
|
||||
Quote:
http://forum.ppcgeeks.com/showthread...highlight=wmdc For me, I have discovered that every time I flash a new ROM, I have to switch to a different USB port. I can go to one I've used previously, but not the most recent one if that makes sense. It probably doesn't...it doesn't even make sense to me. Let me give an example. I use USB port A on Monday. Everything's working great. Tuesday morning, I come in, plug my phone into USB port A and then flash a new ROM. Once I'm through, I need to switch to USB port B because USB port A stops working for me. When I do, everything will work fine. Wednesday morning, I come in, plug my phone into USB port B, and realize I did something wrong on Tuesday, so I flash a new ROM again. After the flash, USB port B won't work for me anymore, but USB port A will once again work. So, I switch back to USB port A and I'm happy. Don't ask me why this is working for me. I haven't a clue, and don't really have enough curiosity about this phenomenon to try to figure it out. Someday MS will get WMDC stable enough that I won't have to do this, I hope. Oh, and I have much better luck using USB ports directly attached to the machine...no hubs.
__________________
In theory, there's no difference between theory and practice. In practice, there is.
|
|
||||
Hey... Luv2chill ....
having a problem with the new 6.1.6965 WMDC and the build OS. For some reason it's not recognizing my device. I've left it in standard mode and also put it in bootloader mode and it still doesn't recognize. What am I doing wrong? I really want to get this working on my vista machine.. but I'll go back to my XP if I needed. in chat room right now if that will help. Daveedem
__________________
EVO 4
Rooted because I don't like the Man telling me what I can and can't do... |
|
||||
Man, this forum is my favorite place that doesn't serve alcohol!
cjbreisch, you are da man! Changed the USB port and ... wham! Sync City. Well, almost wham ... I had to connect and disconnect 3 times, but it's working. Thanks! Quote:
|
|
||||
alright.. who's smoking what here...???
I'm trying to reflash... and getting can't connect messages.. I have 4 more ports to try... will report shortly... BUT come-on.. I know it's MS and all... but this can't be the case... |
|
||||
I think you're problem is different than mine.
I couldn't sync; thought it was something to do with my flashing the rom, but it was just a "new device" plugged into the same port. WMDC was ignoring it until I used a different USB port. You're having problems getting your Vista box to use the kitchen BuildOS software to flash your Apache. So did I. I read how some were getting it to work, but it seems to much work for me. I just used my XP laptop. |
|
||||
Quote:
Here's the error with RUU, Vista, WDMC 6.1.6965 "an unhandled win32 exception occurred in in ROMUpdateUt.exe [5324]. Just-in-time debugging this exception failed with the following error: no installed debugger has just-in-time debugging enabled. in visual studio, just-in-time debugging can be enabled from tools/options/debugging/just-in-time |
|
||||
OK... CJ.. you partly the man... damn MS.
So i resorted back to Modaco's RUU fix. I also switched my USB port and wouldn't you know it... the damn thing is now loading.... reaching for my wine glass.... i need a drink Luv? grr? those more-in-the-know-than-me? I feel like a complete noob. What is it? just typical MS BS? Mother? leave me alone.. I'm in the kitchen cooking..... |
|
|
|