bubbanc

Thanks for the links. The full, non-nLite'd works with no issues everytime. I've left all hardware & drivers in my nLite install and still have issues. And I haven't found a way to re-install the telephony subsystem. I did try copying all the files mentioned in the modem log from the working system to the non-working system, but that didn't work either.

Any thoughts? I have exhausted my ideas of things to try... Thanks, Brian

I did a new install; I left all Drivers, All Hardware Support and all services default. Still fails with the same message as above. These images are running in Parallels software on OS X. I am thinking this doesn't matter since it works fine with the default XP SP2 CD, but not with an nLite created cd. Attached is my config. Thanks, Brian LAST_SESSION.INI

Ok, I even went back and set all services to their defaults. I also enabled more hardware pieces that might be remotely related to USB or Modems. I received the same error message as directly above. The next step is to leave all hardware & drive pieces enabled. I'm attaching the configuration file. Thanks in advance! LAST_SESSION.INI

I can confirm that classic theme doesn't give you a classic start menu. I looked for a classic option under Start Menu and found none. I also don't believe the "Show Small Font's in Start Menu" option works either.

First off, thanks for your assistance! I followed your advice and enabled Multifunctional, Wireless Ethernet, Multiport serial, PCMCIA, USB Ethernet. I also added in the latest RyanVM JAN patch set, so let me know if you want me to remove them and try again. I did receive a different error message this time: "The modem failed to respond. Make sure it is properly connected and turned on. If it is an internal modem or is connected, verify that the interrupt for the port is properly set." 01-31-2007 19:59:20.590 - File: C:\WINDOWS\system32\tapisrv.dll, Version 5.1.2600 01-31-2007 19:59:20.590 - File: C:\WINDOWS\system32\unimdm.tsp, Version 5.1.2600 01-31-2007 19:59:20.590 - File: C:\WINDOWS\system32\unimdmat.dll, Version 5.1.2600 01-31-2007 19:59:20.590 - File: C:\WINDOWS\system32\uniplat.dll, Version 5.1.2600 01-31-2007 19:59:20.590 - File: C:\WINDOWS\system32\drivers\modem.sys, Version 5.1.2600 01-31-2007 19:59:20.590 - File: C:\WINDOWS\system32\modemui.dll, Version 5.1.2600 01-31-2007 19:59:20.590 - File: C:\WINDOWS\system32\mdminst.dll, Version 5.1.2600 01-31-2007 19:59:20.590 - Modem type: Standard Modem 01-31-2007 19:59:20.590 - Modem inf path: mdmgen.inf 01-31-2007 19:59:20.590 - Modem inf section: Gen 01-31-2007 19:59:20.590 - Matching hardware ID: mdmgen 01-31-2007 19:59:20.590 - Opening the modem device failed with error 000005aa I left the services alone since I can enable them after the install. You can see from the screenshot how many I ended up enabling with still no luck (the last one that is disabled that is covered up in the screenshot is wireless zero conf). I also verified that no errors were shown in the Device Manager so the BlackBerry appears to be operating normally. The Blackberry software installs 2 com ports (com 3 & com 4). I have tried this on both of the com ports that it creates, but on the working, regular XPSP2 image, com 3 is the one that works. Both working and non-working images are in the same virtualized environment, so there are no com ports to enable/disable from the BIOS. As you can see from the screenshot, still no luck. Please let me know if you have any additional suggestions for things to include or services to enable. Thanks, Brian LAST_SESSION.INI

FYI, I created another nLite image today but did not add any addon's, patches, updates or drivers and the problem still occurs. This to me points to either an nLite issue or a configuration issue on my part. Attached is my nLite configuration. Please let me know if you see anything that might cause modem/USB/Blackberry issues. Thanks! Brian LAST_SESSION.INI

I'm using latest nLite 1.3RC2, latest RyanVM update pack (January). I don't think the nLite version or RyanVM versions matter, because this issue has been going on since before December with older 1.2 and older RyanVM updates. I cannot for the life of me get the tethered modem to work with an nLite Windows install. I have tried various verisons of Blackberry software which did not work. I have, however, gotten this to work with no issues on an install from a non-nLite XPSP2 image. I have left TAPI in, Modem support in, etc. I get to to the modem section and see the Blackberry modem. When I go into Modem Properties and go do Diagnostics -> Query, I get (see attachment): "The port that the modem is attached to cannot be opened. This may be a result of a hardware conflict. Check the device manager to verify all devices are functional." All devices are functional, as far as I can tell; no issues in device manager. Same services running on each machine (nLite and non-nLite). No errors in Event Viewer! No signs that this should have failed. The failure info in the modem log says this: 01-29-2007 21:12:36.690 - File: C:\WINDOWS\system32\tapisrv.dll, Version 5.1.2600 01-29-2007 21:12:36.690 - File: C:\WINDOWS\system32\unimdm.tsp, Version 5.1.2600 01-29-2007 21:12:36.690 - File: C:\WINDOWS\system32\unimdmat.dll, Version 5.1.2600 01-29-2007 21:12:36.690 - File: C:\WINDOWS\system32\uniplat.dll, Version 5.1.2600 01-29-2007 21:12:36.690 - File: C:\WINDOWS\system32\drivers\modem.sys, Version 5.1.2600 01-29-2007 21:12:36.690 - File: C:\WINDOWS\system32\modemui.dll, Version 5.1.2600 01-29-2007 21:12:36.690 - File: C:\WINDOWS\system32\mdminst.dll, Version 5.1.2600 01-29-2007 21:12:36.690 - Modem type: Standard Modem 01-29-2007 21:12:36.690 - Modem inf path: mdmgen.inf 01-29-2007 21:12:36.690 - Modem inf section: Gen 01-29-2007 21:12:36.690 - Matching hardware ID: mdmgen 01-29-2007 21:12:36.690 - Opening the modem device failed with error 00000002 And from my non-nLite install where this is working: ATQ0V1E0 - OK AT+GMM - BlackBerry IP Modem AT+FCLASS=? - COMMAND NOT SUPPORTED AT#CLS=? - COMMAND NOT SUPPORTED AT+GCI? - COMMAND NOT SUPPORTED AT+GCI=? - COMMAND NOT SUPPORTED ATI1 - Research in Motion / BlackBerry IP Modem ATI2 - Research in Motion / BlackBerry IP Modem ATI3 - Research in Motion / BlackBerry IP Modem ATI4 - Research in Motion / BlackBerry IP Modem ATI5 - Research in Motion / BlackBerry IP Modem ATI6 - Research in Motion / BlackBerry IP Modem ATI7 - Research in Motion / BlackBerry IP Modem This is the exact same hardware as I'm testing in a virtual machine. The only difference is one machine is done with nLite & RyanVM. I am at my wits end in trying to figure this one out. PLEASE PLEASE PLEASE, I'm willing to try anything should someone have a good suggestion. Is there any extra debugging I can turn on to help me track down the problem? Thanks, Brian