Jump to content


  • Content count

  • Joined

  • Last visited

About zzz

  • Rank
    InsanelyMac Protégé

Recent Profile Visitors

2,307 profile views
  1. Hello, back again. This time i purchased a dead cheap x220t in order to try and enjoy some tablet input under osx. x220's have been very pleasing affordable hackintosh computers, I thought id look at the tablet versions and just dived in. x220t's however are showing up for a while now with "no pressure" in various guides, I decided to delve deep, knowing i could get-rid of the tablet worst case, or have a pointer input with at best case pressure. Perhaps we can solve this issue by resolving it in Yosemite and bringing a functional tablet into High Sierra, or worst case El Capitan. Shouts go out to folk progressing things here: http://x220.mcdonnelltech.com/ https://www.reddit.com/r/thinkpad/comments/6b9rua/my_thinkpad_x220_using_macos_in_the_desert_maybe/ https://forum.thinkpads.com/viewtopic.php?t=116064&start=60 Looking out there , there are two models, one with multitouch, one without. Multitouch versions seem to fall on various dead ends. The thinkpad user from thinkpads.com described a process that works with his non-multitouch model, using the driver from wacom, configuring etc and having success. I will ask him for his device and vendor id's to see the difference in models. I will also need his successful configuration too. If you are a non-multitouch user, you could provide me with device and vendor ids for the ISD-V4 or whatever the device is listed as under System Profiler and configuration files for the wacom driver listed here https://forum.thinkpads.com/viewtopic.php?t=116064&start=60 I am understanding this can only be properly configured in Mavericks, and then dragged over to Yosemite. This file could be an important step, to others wanting to use the old wacom driver. I seem to have the multi-touch model. on the Multitouch version I see two instances of ISD-V4 under controllermate, but obviously one device in System Profiler. I suspect this device can be configured with someones non-multitouch version preferences, pulled from ftp://ftp.wacom-europe.com/pub/Mac/cons521-3_int.dmg once installed and configured. Hence asking for such files. On a more positive note, to confirm tablet pressure once and for all with regards to the grey posts i have found out there, it seems both models can give tablet pressure in yosemite. Going by users with the non-multitouch versions success and my recent success with this old machine. I have experimented with throwing a lot of wacom drivers on this machine, to no success, but the stock iohidfamily.kext from yosemite will give tablet pressure in affinity photo, without any drivers installed. In Yosemite. On Multitouch, Mouse offset issues appear when using it in Sierra , but tablet pressure returns - this is due to depreciation of IOHID http://dae.me/blog/2144/on-macos-sierra-support-and-the-future-of-smoothmouse/ I had hoped we could use something like smoothmouse to resolve, perhaps it could be used in El Capitan or the offset resolved, once again, using the wacom driver and configs. So I am making this "the post", to try and resolve this for those wanting to use this laptop to experiment. Right now I have scratchy tablet pressure due to not being able to configure properly. If you do install the wacom driver listed as successful on the multitouch version in yosemite, by default (with using rehabmans voodoops2 etc) middle mouse button behavior causes an immediate log out. Very weird. My machine came with windows pre-installed so I will fire up the windows 10 i have and see if any preferences can be pulled from that. Non-multitouch users: Can you install the wacom driver in yosemite, and pull your configs and share. Multitouch users - try an install of yosemite, fully updated and run affinity photo. Click the brush tool and you will see you have an option for pressure (little brush icon with a radar), this happens without need of wacom software installed. 056a:00e6 -is the device and vendor id for the multitouch, i now need the device and vendor id of the non-multitouch version.
  2. Keywords: Ricoh, PCI, SD, SDXC, VoodooSDXC, HSSDBlockStorage, T61, T61p, R61e. Recently decided to get a T61p running Yosemite: Noticed a heap of people out in the cold with Ricoh based PCI card readers. I am no programmer, but I can google well and I do like to see how kernel extensions work with a bit of tweaking. Noticed the HSSDBlockStorage.kext for JMicron based PCI cards exposes the PCI to JMB38X.kext So I took a look at both kexts and a working kext for Mavericks for the "Ricoh Co Ltd R5C822 SD/SDIO/MMC/MS/MSPro Host Adapter [1180:0822] (rev 21)" (Perfect T61 Hacbook Bundle -Google -HackintoshOSX forums), added values from JMB38X.kext to VoodooSDHC.kext, added values from VoodooSDHC.kext to HSSDBlockStorage.kext and it loaded and read the cards, formatted etc. I dont have source code for HSSDBlockStorage or coding knowledge, however AppleSDXC.kext is out there. I have noticed Slice and Andy Val and a few over at OSXLattitude have been looking at Ricoh based cards. I am hoping this might shine some light. Who knows. What I will say is I own a T61p from '07. Anyone who knows the backstory of Nvidia GPU's from back then knows that they are volatile - prone to atefacts and dieing. So I have to treat my computer with cotton wool, I have probably spent more time keeping this machine stable and looking at the console than most (no offence to those that do/don't). If I didnt do GPU intensive tasks on a volatile GPU I would class this "hack" as OK to pass as a 100% working solution, but on this machine (untested on others -note: some bios's dont report IRQ's properly, FSB, etc etc) when I hit hi triangle counts I can get GPU errors with this "solution/hack". I attribute it to the way the PCIe is handing access to the VoodooSDHC kext. I am talking very high stress situations though. I could run this machine with 0 errors with this hack and use cards IF I didnt tax the GPU to the extreme at times. I'd Imagine a more modern card would work just fine (this is a '07 machine with a GPU undervolt and with its core and clock matched to the gt 8600m 256mb DSDT patched to match - originally fx 570m). What I am hoping is this will help the average user to enable Ricoh cards. Swap out the VoodooSDXC for one that works for you and check the values of the kexts to match yours up, or try a previously working other kext alongside HSSDBlockStorage. Maybe HSSDBlockStorage can be patched with a HEX editor to replace the strings to curb one console nag. Maybe sources for HSSDBlockStorage are out there somewhere.... Once again I am no Coder, just an enthusiast Hacker. I have noticed some people out there using a solution using JMB38X.kext, VoodooSDHC.kext, and VoodooSDHC.kext for their systems already, for other cards. Maybe my method is better or worse. I can do 3D modelling with these kexts, I just cannot game or run huge scenes. If you are willing to face a kernel panic and stress test, maybe theres a fix. I am hoping that this might open up a path to using AppleSDXC on its own - as I own the "Advanced 2503 Dock" and adding ricoh dev ven id's to it opens up this ricoh card reader on that piece of hardware. Happy Hacking and I hope I have made some contribution here, if your ricoh reader is not the same be prepared to edit VoodooSDXC.kext, or try other kexts alongside HSSDBlockStorage looking at what i did inside both. ZZZ Edit: Seems taking content from AppleSDXC.kext and putting them in the zip file attached called "VoodooSDHC.zip" was enough for my Ricoh device. You will need to remove AppleSDXC.kext, fire up the console, use kextutility and observe any messages. In my case it worked just fine, I was able to use 1.1d1 with: <key>OSBundleLibraries</key> <dict> <key>com.apple.iokit.IOPCIFamily</key> <string>2.0.0</string> <key>com.apple.iokit.IOReportFamily</key> <string>1.0</string> <key>com.apple.iokit.IOStorageFamily</key> <string>1.2.7</string> <key>com.apple.kpi.bsd</key> <string>9.0.0</string> <key>com.apple.kpi.iokit</key> <string>9.0.0</string> <key>com.apple.kpi.libkern</key> <string>9.0.0</string> <key>com.apple.kpi.mach</key> <string>9.0.0</string> </dict> <key>OSBundleRequired</key> <string>Local-Root</string> At the end. Archive.zip VoodooSDHC.kext.zip
  3. AMD Radeon R9 M290X

    I am curious as to whether this mobile card will find support? I would like to opt for a high specification laptop if the issues of Nvidias Optimus can be bypassed by going for AMD. I do not need the card for gaming, more gpu related tasks to which this card is suitable.
  4. Newer G4 upgrades

    Just a quick point: the fsb is on the processor so the newer processor will have a slightly better fsb, but an intel mac will outperform these machines easy. I bought a sawtooth purely to service os9 users, also i wanted a cheap machine i could use scsi on and that had pci.
  5. that is one cool motorized chair dude zzz
  6. lightscribe hackintosh

    disclabel and you will need the hp driver found over at lightscribe.com iirc
  7. Slick hackintosh cases

    the white antec case mentioned in the first post is a very nice case (i personally own one due to reading this thread) one comment though - if you intend to use the other bays - use quality white components for the 'mac feel'. Of all the cases i have seen i prefer it - matches the apple components i allready own.
  8. hpet/nx free 10.4.8 kernel hack

    aye good work matey, i too will be giving you my support. i dont think it matters who does what first, i think the enjoyment is in the challenge and the acheivement. xcode 2.4 installed, will be helping all i can mate with future kernel builds. zzz
  9. http://www.osxbook.com/software/iremoted/ this communicates with a real intel mac's built in IR and lists the buttons pressed, i have looked at alot of third party applications (unfortunately most suffer difficulties as they are not universal and therefore suffer problems communicating with the keyboard and or install incompatible drivers) but i think it might be easier to produce something that maps an xbox's pad to frontrow first of all.. the source isnt included btw... back to the mapping issues though: http://homepage.mac.com/walisser/xboxhiddriver/ this is where i beleive sampson got the source to compile an intel mac kext - is anyone able to compile the pref pane (source is inclued in the download btw - to avoid confusion) also another possibility is usb overdrive perhaps? - this i have been told is universal although i havent worked out how to map pad combinations to get frontrow up and running. (my advice is to use the xbox IR and xbox remote, not mix and match other remotes just yet- to avoid confusion.) hmm perhaps this could help: http://www.osxbook.com/forums/viewtopic.ph...2c58ce804bdf0c8 the iremoted deamon communicates with AppleIRController.kext, can that kext be edited to include the intel compiled xbox HID driver? more info: http://www.osxbook.com/book/bonus/misc/frontrow/ btw i post this as i cannot do much myself and merely wish to aid someone willing - mainly as i think its a gret idea for others to benefit from
  10. hey sampson has ported a HID driver for xbox pads/ IR remotes here: http://forum.osx86project.org/index.php?showtopic=8075&hl= anyway to get the IR + remote working with front row? the xbox pad could be another alternative seeing as alot of people use them for games zzz
  11. building a pentium d based system and i would ideally like it in a 1u rackmount - the supplied fan is huge though and im wondering if smaller slimline fans could be used? any ideas?
  12. hi i own an asrock 775i65GV with ich5/ich5r sound, dev/vendor id : 8086:24d5. trying to get sound in a myz 10.4.4 with 10.4.5 ppf iso, running currently 10.4.5, i have choppy sound, seems to be a stutter every 1-5 secs makes for a poor listening experience in itunes... does anyone have any ideas, i have scraped around this site following various guides to no avail. zzz
  13. 10.4.6 ppf released

    it contains a .sh script that can update to 10.4.6 from a working 10.4.5 install the ppf part in the title was misleading - this happened because the original information was thought to be a ppf to update the 10.4.4 restore dmg, i am now informed thats not the case. it has been corrected. there may contain files to patch the dmg to 10.4.5 too, ill get more info off JaS as i dont want to mislead any more... he is around, im realising just how much interest these guys are getting. on a new note, people should describe how to make a working install on: 1/ amd systems, from the right unpatched dvd choice to how to patch correctly to get a working o.s 2/ intel, from the right unpatched dvd choice to how to patch correctly to get a working o.s the rest should then be up to the user, they should be aware that the right choice of motherboard is the result of most issues as we all know apple only supports limited hardware. I feel that the right way to sort alot of **** posts out from newcomers is to describe a step by step guide from unpatched dvd to working o.s, as processor types seem to be what makes getting patched dvds a hassle, and what could result in a better more suited result. feel free to say it again in a new post zzz