• RXTX
• JavaComm

Unfortunately, the current version of JavaComm does not support Windows, and only supports Solaris SPARC, Solaris x86, and Linux x86.  Since I use none of those operating systems, this article will only discuss how to install RXTX in Windows.

UPDATE: 12 Sept 2011 – Thanks to a comment from Kurt Zoglmann, there are instructions on how to do this with a Mac!  I never tried this myself because I don’t have a Mac, but the procedures stated there look good to me (see comments).

A 32 and 64 bit version of the library exists.   I’ve updated this article from when it was first published to include the new locations for where to download the libraries, but I have not gone through the installation of the libraries again, so I’m not surprised if the rest of the content on this page is outdated too.

32-bit version: http://rxtx.qbang.org/wiki/index.php/Download
64-bit version: http://fizzed.com/oss/rxtx-for-java

To install the libraries (instructions from JControl):

1. Copy rxtxSerial.dll to %JAVA_HOME%\bin, (%JAVA_HOME% is the folder where JRE is installed on your system; e.g. c:\Program Files\Java\j2re1.4.1_01)
2. Copy RXTXcomm.jar to %JAVA_HOME%\lib\ext

Once installed, the IDE will need to know where to look for these installed files.  Even though the files exist in the JRE directory, each project needs to know about these files.  More information on this website.

In order to start coding with this library, import gnu.io.*.  For more information about Java Serial Programming, look here.

Happy coding!

Computer Specs:

Intel Core 2 Duo T5250 Processor
2 GB RAM @ 667 Ghz
Intel GM965 Chipset
nVidia GeForce 8600M GT
Dell Wireless 1390 802.11g

Installation

I was lucky enough to only need the Retail Snow Leopard Disc (10A432) and the myHack Installer 1.0.1.  I pretty much followed METHOD 2 in this guide (method 1 didn’t really work out for me, but it might have had something to do with the disc restoration part of the guide):

http://prasys.co.cc/2009/08/installing-snow-leopard-for-osx86/

For the myHack installer, check the box for the kext that says something about PS2 in it.  It will enable the laptop touchpad and keyboard.  Also, read the description for each kext to see if you need it or not.

When I used method 1 in the guide, I had some trouble with an installation error that said “Could not verify BaseSystem.pkg” or something along those lines.  That error appeared at about 10-15% installation progress.  It went away then I used method 2.  I did read somewhere that it may have had to do with the restoration in Disk Utility.  Either way, it worked the second time around.

Once SL was installed, I ran the myHack Installer on my drive to get the Chameleon Bootloader on there so I wouldn’t have to use my USB to boot all the time.  Also, be sure not to install GraphicsEnabler as it will prevent your computer from shutting down completely (more on that later).

Graphics

Since my laptop uses an nVidia card, there is an issue that prevents the computer from shutting down completely if the “GraphicsEnabler” option is used in the myHack Installer.  I believe NVInject, NVKush, and NVDarwin all suffer from this same problem.  What happens is that when the shut down command is invoked, the computer’s screen will turn off, the HD will turn off, but the power stays on.  When the nVidia graphics kexts aren’t used, this problem goes away.

I’ve tried generating an EFI String and loading that with EFI Studio, but it didn’t do the job.  The resolution is still 1024×768 and I have no QE, CI or OpenGL support.  What I did later on was install PC EFI to see if that would fix things (I didn’t really know what I was doing here at this point).  That didn’t really work, but I did later find out that EFI Studio allows me to add boot flags.  I added “Graphics Mode”=”1280x800x32” to the boot flag so now it boots with the proper resolution.  It gives the proper resolution, but still no QE/CI or OpenGL.  This guide has information on how to test for QE (Quartz Extreme) and CI (Core Image): http://prasys.co.cc/tag/enable-qeci/

Another thing I tried was to modify my DSDT to get my graphics card working using this link: http://tonymacx86.blogspot.com/2010/01/advanced-dsdt-fixes-nvidia-graphics.html.  I managed to get the card recognized using the DSDT code, but when I got rid of the graphics kexts, and the boot.plist options as specified in the guide, I lost my graphics acceleration.  I know my DSDT code is working here still since System Profiler tells me what card I have with the exact same names that I gave in the DSDT.  It seems that having graphics acceleration and shutdown/restart working properly just isn’t meant to be.

The tradeoff:

I either could have proper graphics acceleration and no shutdown, OR I could have shut down and no graphics acceleration.  Graphics is the clear winner here, but I still hate having no shutdown.  I have not found a fix for this.

Power Management

There was a problem with high CPU temperatures with the laptop.  I installed the VoodooPowerMini kext located here (http://forum.voodooprojects.org/index.php/topic,1095.0.html)

Audio

After looking for various kexts, I found that VoodooHDA worked for me.  It can be found here (http://www.kexts.com/view/70-voodoohda_(32–_64-bit,_recompiled_by_prasys).html).

Wireless

Works after installation.

USB Ports

They work since it can recognize my mouse and USB drive.

Battery Indicator

I used the VoodooBattery kext located here (http://forum.voodooprojects.org/index.php/topic,1092.0.html)

Card Reader

I don’t use this so I didn’t install the kext for it.  It can be found here: http://www.dailyblogged.com/retail-snow-leopard-installation-guide/ or SD Card Fix (more direct).

Touchpad

I had an issue where I couldn’t tap the touchpad in order for it to “click”.  I fixed this issue by installing the VoodooPS2Controller kext (check the Trackpad option during the installation) (http://forum.voodooprojects.org/index.php/topic,235.0.html).  Then I installed the preference pane (this allows configuring the Trackpad through System Prefs) here http://www.dailyblogged.com/retail-snow-leopard-installation-guide/ (command -f to find it).  I opened System Preferences and pressed the Show All button, and I saw a “Trackpad” option, so I opened it and the option was there.

Webcam

Works after installation.

Conclusion

Everything I listed here works except for video and the card reader.  There are other things like Ethernet, but I don’t really use it.

UPDATE: This set of instructions works for the Office 2010 Technical Preview as well.

Based on: https://answers.microsoft.com/en-us/msoffice/forum/all/trying-to-install-office-2010-but-getting-error/4a5e022f-13f1-42bb-ad66-f6dccfd44d40

To automatically uninstall the 2007 Microsoft Office suite, follow the steps in the following Microsoft Knowledge Base article: http://support.microsoft.com/kb/971179/

How do I uninstall the 2007 Office suites if I cannot uninstall it by using the “Add or Remove Programs” feature?

The steps provided in the ‘More Information’ section of this article provide the details of the removal performed by the solution in 971179.

You may find it easier to follow the steps if you print this article first.

First, verify that you cannot uninstall the 2007 Microsoft Office system by using Add or Remove Programs (or Programs and Features)

To verify that you cannot uninstall the 2007 Microsoft Office system by using Add or Remove Programs (or Programs and Features in Windows Vista), follow these steps.

For Windows XP or Windows Server 2003:

1. Click Start, click Run, type control appwiz.cpl in the Open box, and then press ENTER.
2. Click to select the 2007 Office system product from the application list, and then click Remove.

For Windows Vista:

1. Click Start, type prgrams and features in the Search box, and then press ENTER.
2. Click to select the product to be uninstalled from the listing of installed products, and then click Uninstall/Change from the bar that displays the available tasks.

If you were able to uninstall the 2007 Microsoft Office system by using Add or Remove Programs, you are finished. If you were unable to uninstall the 2007 Microsoft Office system, you may have issues with the Add or Remove Programs dialog box, or some 2007 Microsoft Office components may not be uninstalled. In these cases, you may be unable to reinstall the 2007 Microsoft Office system. Go to the next section to uninstall the 2007 Microsoft Office system by using an alternative method.

If Add or Remove Programs does not uninstall the 2007 Microsoft Office system, use this alternative method to uninstall

Use this method only if the Add or Remove Programs method did not work for you. Using this method does not completely uninstall the 2007 Microsoft Office system. After you use this method, you can reinstall the 2007 Microsoft Office system.

Note You must be logged on to Windows with a user account that is a computer administrator to complete this method. If this is your personal computer, you are likely already logged on with an administrator account. If this is a computer that is part of a network, you might have to ask the system administrator for help.

To uninstall the existing 2007 Microsoft Office system if you cannot uninstall it by using the Add or Remove Programs feature, follow these steps:
Step 1: Remove any remaining Windows Installer packages of the 2007 Microsoft Office system:

1. Click Start, click Run, type installer, and then click OK.
   This process opens the %windir%Installer folder.
2. On the View menu, click Details.
   Important To use the View menu in Windows Vista, you must press the ALT key first to display the menu bar, and then click the View menu.
3. On the View menu, click Choose Details.
4. Click to select the Subject check box, type 340 in the Width of selected column (in pixels) box, and then click OK.
   Note It may take several minutes for the subjects to appear next to each .msi file.
5. For Windows XP or Windows Server 2003, on the View menu, point to Arrange icons by, and then click Subject.
   For Windows Vista, on the View menu, point to Sort By, and then click Subject. In Windows Vista, a User Account Control dialog box may be displayed with the following warning:
   An unidentified program wants access to your computer

   Click Allow when you see this warning message.

6. For each .msi file where the subject is “Microsoft Office Product_Name 2007,” right-click the .msi file, and then click Uninstall.
   Note Product_Name is a placeholder for the name of the 2007 Microsoft Office product.

Step 2: Stop the Office Source Engine service:

1. For Windows XP and Windows Server 2003, click Start, click Run, type services.msc in the Open box, and then click OK.
   For Windows Vista, click Start, click Start Search, type services.msc, and then press ENTER.
2. In the Services window, determine whether the Office Source Engine service is running. If this service is running, right-click Office Source Engine, and then click Stop.
3. Close the Services window.

Step 3: Remove any remaining 2007 Microsoft Office installation folders

1. For Windows XP and Windows Server 2003, click Start, click Run, type %CommonProgramFiles%\Microsoft Shared in the Open box, and then click OK.
   For Windows Vista, click Start, click Start Search, type %CommonProgramFiles%\Microsoft Shared, and then press ENTER.
   Note On a computer that is running a 64-bit version of Windows Vista, type %CommonProgramFiles(x86)%\Microsoft Shared, and then press ENTER.
2. If the following folders are present, delete them:
   • Office12
   • Source Engine
3. For Windows XP and Windows Server 2003, click Start, click Run, type %ProgramFiles%\Microsoft Office, and then click OK.
   Note On a computer that is running a 64-bit version of Windows XP, type %ProgramFiles(x86)%\Microsoft Office, and then press ENTER.
   For Windows Vista, click Start, click Start Search, type %ProgramFiles%\Microsoft Office, and then press ENTER.
   Note On a computer that is running a 64-bit version of Windows Vista, type %ProgramFiles(x86)%\Microsoft Office, and then press ENTER.
4. On the root folder of each hard disk drive, locate and then open the MSOCache folder. If you cannot see the MSOCache folder, follow these steps:
   1. Open Windows Explorer, and then on the Tools menu click Folder Options.
   2. Click the View tab.
   3. In the Advanced settings pane under Hidden files and folders, click Show hidden files and folders.
   4. Click to clear the Hide protected operating system files check box, and then click OK.
5. Open the drive_letter:\MSOCache\All Users folder, and then delete every folder that has the following text in the folder name: 0FF1CE

   Note This text contains a zero and a one for the letters “O” and “I.”

Step 4: Remove any remaining 2007 Microsoft Office installation files

1. For Windows XP and Windows Server 2003, click Start, click Run, type %appdata%\microsoft\templates, and then click OK.
   For Windows Vista, click Start, click Start Search, type %appdata%\microsoft\templates, and then press ENTER.
2. Delete the following files:
   • Normal.dotm
   • Normalemail.dotm
3. For Windows XP and Windows Server 2003, click Start, click Run, type %appdata%\microsoft\document building blocks\Language_ID, and then click OK.
   For Windows Vista, click Start, click Start Search, type %appdata%\microsoft\document building blocks\Language ID, and then press ENTER.
   Notes
   • If you cannot open this folder because the folder does not exist, go to step 6.
   • Language_ID is a placeholder for the four-digit number that represents the language of the 2007 Microsoft Office system. For example, if you use the English version of the 2007 Microsoft Office system, the Language_ID value is 1033. If the Language_ID is not known, type %appdata%microsoftdocument building blocks, and then open the subfolder in that location.
4. Delete the Building blocks.dotx file.
5. For Windows XP and Windows Server 2003, click Start, click Run, type %temp%, and then click OK.
   For Windows Vista, click Start, click Start Search, type %temp%, and then press ENTER.
6. On the Edit menu, click Select All.
7. On the File menu, click Delete.
8. For Windows XP and Windows Server 2003, click Start, click Run, type %AllUsersprofile%\Application Data\MicrosoftOfficeData, and then click OK.
   For Windows Vista, click Start, click Start Search, type %AllUsersprofile%\Application DataMicrosoftOfficeData, and then press ENTER.
9. Delete only the Opa12.dat file.

Step 5: Remove the registry subkeys of the 2007 Microsoft Office system

Important: This section, method, or task contains steps that tell you how to modify the registry. However, serious problems might occur if you modify the registry incorrectly. Therefore, make sure that you follow these steps carefully. For added protection, back up the registry before you modify it. Then, you can restore the registry if a problem occurs. For more information about how to back up and restore the registry, click the following article number to view the article in the Microsoft Knowledge Base: http://support.microsoft.com/kb/322756/

1. Locate and then delete the registry subkeys of the 2007 Microsoft Office system if they are present. To do this, follow these steps:
   1. For Windows XP and Windows Server 2003, click Start, click Run, type regedit, and then click OK.
      For Windows Vista, click Start, click Start Search, type regedit, and then click OK.
   2. Click the following subkey:
      HKEY_CURRENT_USER\Software\Microsoft\Office\12.0
   3. On the File menu, click Export, type DeletedKey01, and then click Save.
   4. On the Edit menu, click Delete, and then click Yes to confirm the deletion.
   5. For each registry subkey in the following list, repeat steps 1a through 1d. Change the name of the exported key by one for each subkey.
      For example, type DeletedKey02 for the second key, type DeletedKey03 for the third key, and so on.
      Note In the following registry keys, the asterisk character (*) represents one or more characters in the subkey name.
      32-bit versions of Microsoft Windows:
      • HKEY_CURRENT_USER\Software\Microsoft\Office\12.0
      • HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\Office\12.0
      • HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\Office\Delivery\SourceEngine\Downloads\*0FF1CE}-*
      • HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\Windows\CurrentVersion\Uninstall\*0FF1CE*
      • HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\Windows\CurrentVersion\Installer\UpgradeCodes\*F01FEC
      • HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\Windows\CurrentVersion\Installer\UserData\S-1-5-18\Products\*F01FEC
      • HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Services\ose
      • HKEY_CLASSES_ROOT\Installer\Features\*F01FEC
      • HKEY_CLASSES_ROOT\Installer\Products\*F01FEC
      • HKEY_CLASSES_ROOT\Installer\UpgradeCodes\*F01FEC
      • HKEY_CLASSES_ROOT\Installer\Win32Assemblies\*Office12*

        64-bit versions of Microsoft Windows:

      • HKEY_CURRENT_USER\Software\Microsoft\Office\12.0
      • HKEY_LOCAL_MACHINE\SOFTWARE\Wow6432Node\Microsoft\Office\12.0
      • HKEY_LOCAL_MACHINE\SOFTWARE\Wow6432Node\Microsoft\Office\DeliverySourceEngineDownloads\*0FF1CE}-*
      • HKEY_LOCAL_MACHINE\SOFTWARE\Wow6432Node\Microsoft\Windows\CurrentVersion\Uninstall\*0FF1CE*
      • HKEY_LOCAL_MACHINE\SOFTWARE\Wow6432Node\Microsoft\Windows\CurrentVersion\Installer\UpgradeCodes\*F01FEC
      • HKEY_LOCAL_MACHINE\SOFTWARE\Wow6432Node\Microsoft\Windows\CurrentVersion\Installer\UserData\S-1-5-18\Products\*F01FEC
      • HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Services\ose
      • HKEY_CLASSES_ROOT\Installer\Features\*F01FEC
      • HKEY_CLASSES_ROOT\Installer\Products\*F01FEC
      • HKEY_CLASSES_ROOT\Installer\UpgradeCodes\*F01FEC
      • HKEY_CLASSES_ROOT\Installer\Win32Assemblies\*Office12*
2. Locate the following registry subkey:
   HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\Windows\CurrentVersion\Uninstall

   Note On a computer that is running a 64-bit version of Windows, locate the following registry subkey instead:

   HKEY_LOCAL_MACHINE\SOFTWARE\Wow6432Node\Microsoft\Windows\CurrentVersion\Uninstall
3. On the File menu, click Export, type UninstallKey01, and then click Save.
4. Under the Uninstall subkey that you located in step 2, click each subkey, and then determine whether the subkey has the following value assigned to it:
   • Name: UninstallString
   • Data: file_name path\Office Setup Controller\Setup.exe path
     Note In this example, file_name is a placeholder for the name of an installation program, and path is a placeholder for the file path.
5. If the subkey contains the name and the data that are described in step 4, click Delete on the Edit menu. Otherwise, go to step 4.
6. Repeat steps 4 and 5 until you locate and then delete every subkey that matches the name and the data that are described in step 4.
7. Close Registry Editor.

Step 6: Restart the computer

Restart the computer. If the uninstall was successful, you are finished and can now reinstall the 2007 Microsoft Office system if you want. If the uninstall was not successful, go to the “Next Steps” section.

Additional registry information

HKEY_CURRENT_USER\Software\Microsoft\Office\Common\UserInfo

Shadow subkeys for Windows Server 2003 and for earlier versions of Windows Server:

HKEY_LOCAL_MACHINE\Software\Microsoft\Windows NT\CurrentVersion\Terminal Server\Install\Software\Microsoft\Office\12.0

Shadow subkeys for Windows Server 2008:

HKEY_LOCAL_MACHINE\Software\Microsoft\Windows NT\CurrentVersion\Terminal Server\Install\Software

Source: http://support.microsoft.com/default.aspx/kb/928218

Today was supposed to be the day for me to catch up on homework since I had missed a week of class due to my Class 5 road test and my gum graft surgery.  Ivan was nice enough to lend me his notes.  Rather than doing homework today, I decided that I was fed up with Solidworks 2008 not running properly on my Windows 7 x64.

I had previous downloaded the SP4.0 for Solidworks 2008 in hopes that it will allow me to run it on my computer.  To try to get that update to work I would have to install Solidworks 2008 SP0.0.  Due to an unknown reason it would not install on my computer.  Despite the fact that Solidworks would say ‘this program does not support Vista x64’, I had gotten it to install by setting the compatibility mode.  This time around, the installer simply got stuck.

I then thought of alternate methods of getting the program on my computer.  I looked to my virtual machine, which was my temporary solution.  It ran Windows XP and could barely run SW08.  I tried to send the files through the network.  I couldn’t send the files through with a hard drive since it was being used to install the program (yes, the installer was stuck, but I left it running to see if it would respond).  I had trouble sending the files through the network since I had disabled all the network services on the virtual machine to save memory.

A few hours later I still did not have Internet back, but I did however have access to the LAN.  That was all I needed.  While doing the network transfer, an idea hit me.  I turned off Bitdefender and the Solidworks install worked.

After the install, I immediately updated the installation to SP4.0.  I cracked the program as was instructed by the readme.  The program still didn’t work.  I was not shocked.  It told me that it could not find license information.  I figured that it was a side effect of the 64 bit OS.  I took another look at my patch files and saw that it was a 32 bit patch (the title never said).  I looked for x64 versions of SW08 on eMule, but could not find any fast downloads.

Later on an idea for a fix hit me.  I realized that the 32 bit programs were stored in ‘Program Files (x86), which meant I put the license file in the wrong place.  It was supposed to go into ‘C:Program FilesSolidWorks’. I missed the x86 part.  I changed that and ran the program again.  Still no good.  I looked in the registry to see if my registry keys were correct and I stumbled upon the folder where 32 bit software registry entries were stored.  I then realized that my registry info had to go in there instead.  I fixed that and tried it one more time.  It was still no good.  Then i thought, ‘if there was a place for 32 bit registry keys, would that apply for system32 as well?’  Turns out I was correct.  I put the dll file in ‘c:WindowsWow6432’.  I ran SW again and it works.  I felt like a total genius.