[PoNi]

Yes I have down some searching before I started a new topic. And it seems that some ppl have BD 4.2 running on Vista RC1. But i get an error when running "BlackBerry_Desktop_Software_ENG.msi"

It says that "The InstallScript Engine is missing from this machine. If available, please run ISScript.msi, or contact support."

Did anyone else get this error? How do I get around it.

[illmaticone]

i get this with xp pro

[gresch]

if you just downloaded the client software, there is a bug in it that is preventing it from loading the isscript.msi. I'm trying to find a workaround right now.... bbl.

[wibbly]

Here too. Two machines. Both XP Pro.

[wibbly]

Ok. Got a messy work around. Install Destop Manager 4.2 first. Then the new Device Manager installed, wiping out the Desktop Manager as it did so. Then I could reinstall the Desktop Manager again, which I think left the new Device Manager in place.

Doh!

[tyrnight]

Install the Blackberry Device manager with these settings first:
I have Vista RC1 5728 and I had to turn off UAC (User Account Control) in order for this to work.. its under user account settings

then I installed the desktop software second

It installed with out issue.. I dont know where that option is in XP Pro.

[cfjacksn]

If you are trying to install the .MSI version, you'll have a problem when installing on XP Pro. Make sure you download and install the English-only version. That's an EXE file and installs with no problems on XP Pro.

[MasterDecker]

I've had zero problems with BOTH of my XP installations (SP2). BUT on my desktop machine I hav a cradle (USB powered) and I constantly get the same error "USB is not giving enough power, check your installation." type message. Eh it still charges in the cradle, just a tad bit slower. BUT on the XP drive, there are AERO conflicts or errors.

I'm using BB DTM 4.2, and the latest BB firmware from Cellular 1 (Dobson).

[Tsuma]

Originally Posted by gresch

if you just downloaded the client software, there is a bug in it that is preventing it from loading the isscript.msi. I'm trying to find a workaround right now.... bbl.

I got the missing installscrip ( update isscript.msi ) error on my machine, but I was running the installer from deep on my hard drive's path.

After I deleted:
C:\Program Files\Common Files\InstallShield\Driver\11 and
C:\Program Files\Common Files\InstallShield\Driver\1150

and placed the unzipped installation in a shorter path, the installer ran fine.