DisplayLink Forum - View Single Post

kickliquid · 09-27-2009, 06:00 AM

So I finally managed to get my Mimo Display to work. The method and approach that I took to resolve the issue could be very problematic to others willing to try it as well as that everything works fine except one of my Applications called Miro, which is a Video Podcast App stopped working. So proceed with caution and heed my warning when I say this could potentially have detrimental effects on your system. I just happened to be lucky and it only affected one minor application for me. Thats not to say that it will cause problems you might have none at all try it out if you are desperate or just wait until the Displaylink guys write the next driver. I am hoping in writing this that it provides insight into what could be causing the problems

Anyways as previously stated in earlier posts in this thread I was tinkering around with the preference files tweaking the little code that I knew and I even copy and pasted the DisplayLink folder that didn't install when I used the DisplayLink Driver installer for 1.5b. It should have created a folder called DisplayLink in the /Library/Application Support/ but it didn't

So I decided to take a different approach. Knowing that the display worked for me in 10.6.0 due to my experimentation with a cloned backup of a previous Snow Leopard install I decided to do a custom reinstall of the "core system files". Meaning all of my preferences and application settings and media would stay the same but the core files would be reverted back to 10.6.0, it would be like taking a pimped out car and changing the engine. Everything looks the same but the engine has been reverted back to its original state. Something in my core file system must have changed during my initial 10.6.0 upgrade from Leopard to Snow Leopard to the 10.6.1 install.

So I booted into my Snow Leopard Disc Install, clicked through the motions of picking the Language, etc and came to the part where you can customize the install. I clicked on that and "unchecked" all the choices except for "core system files" In fact that choice is grayed out so you can't even uncheck it. Clicked next and proceeded with the install. 30 - 40 minutes later it rebooted into 10.6.0 with all of my files in tact, I came back to the Displaylink website and reinstalled the 1.5b4 drivers and rebooted one last time and Voila!!! it worked.

Feeling ballsey I deiced to experiment some more and I went to the System Preferences updater and downloaded the 10.6.1 update, restarted, and Voila!! it still worked. I was now running the Display under 10.6.1 for the first time, but of course without consequence as previously mentioned with my Miro application.

I hope this gives insight into what could be causing this issue, so that other people with the same problem can at least have a quick work around for now until new drivers/software are written to circumvent the drawbacks. If anyone wants to try this I must once again claim no responsibility on the potential problems it may cause for you as that you are reverting the "core system files" back to a previous version and it could cause some serious headaches. I was fortunate to only have minor issues and for all I know it might not even have any affect on you whatsoever.

Personally something like this always brings a good challenge for me. Im the type that loves to tinker and solve problems, it makes the solution that much more rewarding, but I can see where some people who just want it to work especially after paying $120 dollars, it can be a frustrating dilemma. Most people just want it to work right out of the box as I myself expected it too do as well, but when it didn't it gave me an oppurtunity to put on my tinkering hat. Others will be less forgiving and I hope Mimo USB Monitors get better support for their hardware in the future. I understand that it is still in a beta phase but I didn't know that intially or I might have been more apprehensive to buying it. Of course you guys are in the business of trying to sell as much of these as possible but I'm just saying I think you might want to at least display that fact and if you did then disregard this statement and I should learn to read all the fine print better but as far as I remember I don't remember anywhere it saying that the drivers were still in a Beta phase. A direct honest approach to your customer's is always the best approach I say.

Anyways if anyone has any questions or issues with how I did this work around please message me or just reply to this post as that I subscribe to this thread.

P.S. I have been running TweetDeck on my Mimo Display now fore a few days an it is fantastic!!!!!

09-27-2009, 06:00 AM	#5
kickliquid Junior Member Join Date: Sep 2009 Posts: 4	Resolution So I finally managed to get my Mimo Display to work. The method and approach that I took to resolve the issue could be very problematic to others willing to try it as well as that everything works fine except one of my Applications called Miro, which is a Video Podcast App stopped working. So proceed with caution and heed my warning when I say this could potentially have detrimental effects on your system. I just happened to be lucky and it only affected one minor application for me. Thats not to say that it will cause problems you might have none at all try it out if you are desperate or just wait until the Displaylink guys write the next driver. I am hoping in writing this that it provides insight into what could be causing the problems Anyways as previously stated in earlier posts in this thread I was tinkering around with the preference files tweaking the little code that I knew and I even copy and pasted the DisplayLink folder that didn't install when I used the DisplayLink Driver installer for 1.5b. It should have created a folder called DisplayLink in the /Library/Application Support/ but it didn't So I decided to take a different approach. Knowing that the display worked for me in 10.6.0 due to my experimentation with a cloned backup of a previous Snow Leopard install I decided to do a custom reinstall of the "core system files". Meaning all of my preferences and application settings and media would stay the same but the core files would be reverted back to 10.6.0, it would be like taking a pimped out car and changing the engine. Everything looks the same but the engine has been reverted back to its original state. Something in my core file system must have changed during my initial 10.6.0 upgrade from Leopard to Snow Leopard to the 10.6.1 install. So I booted into my Snow Leopard Disc Install, clicked through the motions of picking the Language, etc and came to the part where you can customize the install. I clicked on that and "unchecked" all the choices except for "core system files" In fact that choice is grayed out so you can't even uncheck it. Clicked next and proceeded with the install. 30 - 40 minutes later it rebooted into 10.6.0 with all of my files in tact, I came back to the Displaylink website and reinstalled the 1.5b4 drivers and rebooted one last time and Voila!!! it worked. Feeling ballsey I deiced to experiment some more and I went to the System Preferences updater and downloaded the 10.6.1 update, restarted, and Voila!! it still worked. I was now running the Display under 10.6.1 for the first time, but of course without consequence as previously mentioned with my Miro application. I hope this gives insight into what could be causing this issue, so that other people with the same problem can at least have a quick work around for now until new drivers/software are written to circumvent the drawbacks. If anyone wants to try this I must once again claim no responsibility on the potential problems it may cause for you as that you are reverting the "core system files" back to a previous version and it could cause some serious headaches. I was fortunate to only have minor issues and for all I know it might not even have any affect on you whatsoever. Personally something like this always brings a good challenge for me. Im the type that loves to tinker and solve problems, it makes the solution that much more rewarding, but I can see where some people who just want it to work especially after paying $120 dollars, it can be a frustrating dilemma. Most people just want it to work right out of the box as I myself expected it too do as well, but when it didn't it gave me an oppurtunity to put on my tinkering hat. Others will be less forgiving and I hope Mimo USB Monitors get better support for their hardware in the future. I understand that it is still in a beta phase but I didn't know that intially or I might have been more apprehensive to buying it. Of course you guys are in the business of trying to sell as much of these as possible but I'm just saying I think you might want to at least display that fact and if you did then disregard this statement and I should learn to read all the fine print better but as far as I remember I don't remember anywhere it saying that the drivers were still in a Beta phase. A direct honest approach to your customer's is always the best approach I say. Anyways if anyone has any questions or issues with how I did this work around please message me or just reply to this post as that I subscribe to this thread. P.S. I have been running TweetDeck on my Mimo Display now fore a few days an it is fantastic!!!!! Last edited by kickliquid; 09-27-2009 at 06:32 AM.