sapinst hang at "import java dump" stage when installting SAP NetWeaver 7.0

When installting SAP NetWeaver 7.0 on HP-UX 11.23, the sapinst comes to an halt. A java process "/opt/java1.4/bin/java -classpath /tmp/sapinst_instdir/NW04S/SYSTEMORA/CENTRAL/ASinstall/sharedlib/launcher.jar... uses 100% CPU not not doing anything)

Your JDK is 1.4.2_10

there is a problem in the Java VM 1.4.2_10 that will cause the installation to hang at this stage. It has been reported on Sun Solaris, but not on HP-UX yet. Apparently it affects HP-UX (IA64) too.

So, upgrade to 1.4.2_13 (patch 14,15,16 has know issue with Kerbose authentication). 1.4.2_17 should work too. But don't forget the installation guide tells you Java 5.0 is NOT supported.

OK Good luck.

VMWare player

It may because of the opensource EMUs like QEMU, VMWare player 2.0 is released as open source software.
To retain some value to its VMWare Workstation, EMC kept VMWare player to be "play" only, you don't have GUI to configure a Virtual Machine.

Ironically, the configuration of the VM (the vmx file) is a plain text file. So you know if you are handy enough, you can do without a GUI. (well, you'd better by their stuff as I own their stock).

For you to get a quick jump start on that, here is a sample vmx configuration file enables most (read: not all) of the features available to VMWare Player 2.0


### sample vmx file ###
config.version = "8"
virtualHW.version = "4"
scsi0.present = "TRUE"
memsize = "512"
MemAllowAutoScaleDown = "FALSE"
ide0:0.present = "TRUE"
ide0:0.fileName = "GL_WXP2C623A.vmdk"
ide1:0.present = "TRUE"
ide1:0.fileName = "auto detect"
ide1:0.deviceType = "cdrom-raw"
floppy0.fileName = "A:"
ethernet0.present = "TRUE"
usb.present = "TRUE"
sound.present = "FALSE"
sound.virtualDev = "es1371"
sound.fileName = "-1"
sound.autodetect = "TRUE"
displayName = "SAP IT Office Image - GL_WXP2C623A"
guestOS = "winxppro"
nvram = "winxppro.nvram"
ide1:0.autodetect = "TRUE"
floppy0.startConnected = "FALSE"
workingDir = ""
toolScripts.afterResume = "TRUE"
toolScripts.beforeSuspend = "TRUE"
ide0:0.redo = ""
ethernet0.addressType = "generated"
uuid.location = "56 4d 3c e6 4c ee 29 a3-f6 26 00 51 eb 87 50 70"
uuid.bios = "56 4d 3c e6 4c ee 29 a3-f6 26 00 51 eb 87 50 70"
uuid.action = "create"
ethernet0.generatedAddress = "00:0c:29:87:50:70"
ethernet0.generatedAddressOffset = "0"
ide1:0.startConnected = "FALSE"
tools.syncTime = "FALSE"
annotation = "SAP IT Office Image - GL_WXP2C623A"
floppy0.present = "FALSE"
isolation.tools.hgfs.disable = "TRUE"

ethernet0.connectionType = "bridged"

checkpoint.vmState = ""

virtualHW.productCompatibility = "hosted"
tools.upgrade.policy = "manual"

extendedConfigFile = "winxppro.vmxf"
sharedFolder.option = "alwaysEnabled"
sharedFolder0.present = "TRUE"
sharedFolder0.enabled = "TRUE"
sharedFolder0.readAccess = "TRUE"
sharedFolder0.writeAccess = "TRUE"
sharedFolder0.hostPath = "C:\"
sharedFolder0.guestName = "C"
sharedFolder0.expiration = "never"
sharedFolder.maxNum = "1"

Microsoft IntelliMouse for Bluetooth on Mac OS X Tiger

It has long been talked about: Microsoft IntelliMouse for Bluetooth and Mac OS X.

I can confirm 2 things for you:
1) the IntelliMouse DOES work with Mac OS X. And its dongle works in Mac OS X too. However, since the dongle is Bluetooth 2.0, it only works in Tiger, not Panther. And it's right, you don't need special drivers, Mac recognize it.
2) The dongle does NOT support headset profile. Hardware wise not. While in Windows, the MS driver does not tell you if this is a driver problem or a hardware issue. Mac tells you right a way. "The hardware does NOT support headset profile". So save you some time, don't bother download wincomm etc.

One good thing about Mac is it comes with generic drivers for many devices. Nowadays, most brand-named products are actually OEM of some very generic stuff and you know Microsoft is not a chip maker, so. . .

Yeah, sure enough, once you connect your MS Bluetooth 2.0 dongle for the mouse to Mac OS X Tiger (either intel or PowerPC) it is recognized and started. You can pair the mouse easily.

When you try to add device and choose headset, you will be told the hardware does not support this profile.

So, kudu to the Mac! You can use Microfot IntelliMouse for Bluetooth even though Microsoft says "support Windows ONLY". Yeah! Who trust Microsoft! Well holdon on that statement, Microsoft said the dongle does not support headset, and it is true, it does not!.