Page 1 of 1

Will our MacNTouch's fit in the new MacBook Pro?

PostPosted: 13 Jan 2006, 19:30
by ibrandt
The keyboard looks the same, and I haven't read anything to the contrary. It looks like the USB port on the right side has moved aft slightly.

I know it has to end someday, but hopefully not quite yet!

PostPosted: 09 Aug 2006, 05:28
by nomaded
From looking at the instructions to remove the upper part of the case, I would say that the chances of a Silver MacNTouch fitting is pretty good. The builtin keyboard looks like it would be removed in a similar manner as in the Oct2005 PowerBook (http://www.ifixit.com/Guide/64.4.0.html).

PostPosted: 09 Aug 2006, 15:33
by -jeffB
Good... LORD! I knew I was spoiled with my TiBook, but I didn't know keyboard removal was THAT bad for the new machines!

But now I've got a MacBook, with exactly zero chance of replacing the keyboard, even if I came into posession of a MacNTouch. :-/ Maybe somebody will come up with a hack to get better gesture recognition out of the trackpad...

PostPosted: 10 Aug 2006, 14:47
by ken gray
"Maybe somebody will come up with a hack to get better gesture recognition out of the trackpad..."

or maybe Steve will quit being a patent whore and start selling FW keyboards again.

My fiance got me a 15" MacBook Pro

PostPosted: 18 Feb 2007, 08:36
by Minox
My fiance got me a 15" MacBook Pro, using my home-made cable and my MacNTouch - i installed it and it works fine.

I posted pictures here: http://www.tycomsystems.com/fingerworks/mbp

XWinder works fine but the Multi-Touch utilities die right after loading :-(

PostPosted: 18 Feb 2007, 12:02
by ivanw
You should get some useful error message from the following procedure:
(As I am with Windows, I can't be sure about details but I know you can do that with Java.)

Create a shell script in the folder where your FW utility has been installed. (You should see there a file named lax.jar.)
Copy&Paste this launch code into a shell script named something like mu.sh and make it executable (i.e. chmod a+x mu.sh)
Code: Select all

 SEP=":" # for Mac Os / Unix

CP=lax.jar
CP=$CP$SEP"lib/FW_defaults.jar"
CP=$CP$SEP"lib/jdom/jdom.jar"
CP=$CP$SEP"lib/jdom/xerces.jar"
CP=$CP$SEP"lib/jh.jar"
CP=$CP$SEP"lib/jusb/jusb.jar"
CP=$CP$SEP"lib/upgredit.jar"
CP=$CP$SEP"lib/utility_help.jar"
java -classpath $CP fingerworks.firmup.UtilityLauncher

I don't know how to do that with Mac OS but the idea is to have a chance to collect error mesages from a command-line console.

I don't know how comfortable you are with this level of details on Mac OS but someone here who is could be more specific about all this...

-ivan

jusb error

PostPosted: 18 Feb 2007, 16:59
by Minox
Exception in thread "main" java.lang.UnsatisfiedLinkError: no jusbMacOSX in java.library.path
at java.lang.ClassLoader.loadLibrary(ClassLoader.java:1682)
at java.lang.Runtime.loadLibrary0(Runtime.java:822)
at java.lang.System.loadLibrary(System.java:992)
at usb.macosx.MacOSX.getHost(MacOSX.java:86)
at usb.macosx.MacOSX.createHost(MacOSX.java:59)
at usb.core.HostFactory.maybeGetHost(HostFactory.java:141)
at usb.core.HostFactory.getHost(HostFactory.java:124)
at fingerworks.firmup.k.<init>(Unknown Source)
at fingerworks.firmup.UtilityLauncher.<init>(Unknown Source)
at fingerworks.firmup.UtilityLauncher.main(Unknown Source)

Now the app launches but doesn't see the macntouch. baby steps huh?

:)

Re: jusb error

PostPosted: 18 Feb 2007, 17:23
by ivanw
Minox wrote:Exception in thread "main" java.lang.UnsatisfiedLinkError: no jusbMacOSX in java.library.path
at java.lang.ClassLoader.loadLibrary(ClassLoader.java:1682)
(...)
Now the app launches but doesn't see the macntouch


Java and you said exactly the same thing, each with his own words!

* USB Java Native Interface library is missing

That means that we have to find a jusbMacOSX.so library file (the Unix flavor of Dynamically Linked Library)...

The catch is that USB handling may have changed for the version of Java currently installed with Mac OS.
:arrow: This means that we have to find someone who can dig one step further on this platform...

It's all about LD_LIBRARY_PATH environment and such kind of things :?