Latest wine issues[SOLVED]

did an upgrade yesterday and wine was updated. wine-1.1.14-1
now I get this error:
wine client error:0: version mismatch 380/381.
Your wineserver binary was not upgraded correctly,
or you have an older one somewhere in your PATH.
Or maybe the wrong wineserver is still running?
I was using it minutes before the upgrade...
Last edited by funkmuscle (2009-01-31 16:27:38)

I just upgraded it with wine running and there are no problems after relaunching it.
Your problems is the old one is still running:
pkill wine
pkill exe
htop or pstree
I have seen the error message when I had several different wine binaries and tried to launch different apps with different binaries. So you can only have 1 wine server running that is specific to the binary used to launch it.
Last edited by Procyon (2009-01-31 16:03:33)

Similar Messages

OTA Update 4.08.605.2 "Rebooting Now..." Issue - SOLVED!

After so many tries and frustration I finally came across the information below and it worked like a charm
http://forums.androidcentral.com/verizon-droid-incredible/134246-second-gb-update-patch-wont-reboot-issue-solved.html
Can't say this will work for everyone, but it worked for me.
Boot into recovery
Press and hold Power, Choose "Restart" option
When screen turns off, press and hold Volume Down and Power
When the white HBOOT screen appears, use the volume button to move down to “RECOVERY.”
Press the Power button to select “RECOVERY.”
When the triangle and exclamation appears, hold the Volume Up and Power button at the same time.
Using the volume button, scroll down to “Wipe cache partition” and select it.
Select "Reboot system now"
You can now wait for the update to show up again, or try one of the methods in the post: For those who want the second GB update/patch to get the update again. It should reboot this time. Beware, it will stay at the Droid Eye screen after reboot for a while (~5 mins), but eventually, it did get installed. Be sure to make a lot of space for it though...

The restart option that AmDroid is talking about is not on the regular phone menu. Please read his post carefully. What he is talking about is in an advanced recovery based menu option.
Also, I was on 2.2 and the clear cache set date and time forward trick did not work for me to get the udpate. The clear cache and set date and time forward trick seems to mostly work if you are already on 4.06 software version and want to get the 4.08 software version.
For those on 2.2, patience is warranted! However, if you really cant wait and want to go the 4.06 update manually, you can search Android Forums dot com for manually install gingerbread. And don't worry about the article talking about being rooted. You dont need to be rooted. The instructions will work for a stock phone too. As soon as you do the manual 4.06, the 4.08 update will show up immediately.
Hope this helps!

Hi all ...I would like to add a language that is not available in Photoshop cc2014 .. My computer writes it but backwards .. How can I have this issue solves?

hi all ...I would like to add a language that is not available in Photoshop cc2014 .. My computer writes it but backwards .. How can I have this issue solves?

What language are you talking about? You might need to enable Edit/Preferences/Type/Middle Eastern and South Asian for proper display.

Compact 2013 Interrupt Issue Solved

As flagged as a comment to the post here, "My iST isn't called", there is a solution in the pipeline (as an update) for ARM interrupt issue. The issue is that interrupts that are close to timer ticks get lost. There is a complete discussion
of this on my blog at:
http://embedded101.com/Blogs/David-Jones/entryid/586/Windows-Embedded-Compact-2013-Interrupt-Issue-Solved
Cheers David Jones
Embedded MVP

As flagged as a comment to the post here, "My iST isn't called", there is a solution in the pipeline (as an update) for ARM interrupt issue. The issue is that interrupts that are close to timer ticks get lost. There is a complete discussion
of this on my blog at:
http://embedded101.com/Blogs/David-Jones/entryid/586/Windows-Embedded-Compact-2013-Interrupt-Issue-Solved
Cheers David Jones
Embedded MVP

Latest Wine breaks World of Warcraft

Latest wine (1.7.44-2) will not run my World of Warcraft install. Downgrading (1.7.44-2 => 1.7.43-1) causes it to work again.
When I first launched it after updating, I saw two windows with 0 height with titles like "wine crash report". I couldn't expand them or anything to read them, and wine had all warnings disabled so I didn't see any terminal output.
After that, I was not able to reproduce getting those two windows. Now, launching it just reports:
Unhandled page fault on write access to 0x00000000 at address 0x7f6c4685f6d7 (thread 0021), starting debugger...
After downgrading, it just works again.
The command I use to launch it normally is "WINEDEBUG=-all __GL_THREADED_OPTIMIZATIONS=1 wine 'Wow-64.exe' -opengl".
Anyone else seeing this behavior and/or have ideas for a fix?
I'm using a GTX680 with the proprietary nvidia drivers. Rest of the system is pretty standard.

There's https://bugs.archlinux.org/task/45199 and https://bugs.archlinux.org/task/45246 .

Workfow latest date issue

Hi All
Recently we have implemented certain changes in Workflow to calculate the Escalation dates based on Factory calendar. This functionality seem to be working fine in Dev and QAS Systems.
After deploying to production, we have noticed that system is not deriving escalation latest end date correctly till 10AM and afterwards it derives correctly. The difference is around 10hrs. If workflow is triggered before 10am it seem to be deriving the yesterday's date to calculate Escalation dates, which is resulting a day less in the latest start date.
Example:
System date: 24/06/2010
Escalation day : Work item creation/system date + 3 Days = 29/06/2010
FM Called in run time: END_TIME_DETERMINE
Latest date derived results: 28/06/2010
This functionality is working fine in Dev and QAS System and problem seem to be only in Production. Our Production landscape includes 5 App servers and 1 Db server.
Moreover, when we tried looking at the results of SWW_WI_DEADLINES_READ, Return parameter SWWWIDEADL-WI_LSD
writes 28/06/2010 whereas SWWSWIDEAD-WI_LSD writes 29/06/2010 which is confusing.
Please help in resolving the issue.
Regards
Kumar
Please note that issue is same as thread posted below. But not sure what is the resolution.
Workflow Deadline Monitoring Latest End - issue
Edited by: Karun Kumar on Jun 24, 2010 9:29 AM

Hi Aditya
Thanks for the response. FM END_TIME_DETERMINE is seem to be working perfectly. Main task and subtasks and relevant logs are updated with correct creation dates etc.
Internally system is not updating SWWWIDEADL-WI_LSD with correct latest start date. We can see the results through FM SWW_WI_DEADLINES_READ, Return parameter SWWWIDEADL-WI_LSD
writes 28/06/2010 whereas SWWSWIDEAD-WI_LSD writes 29/06/2010 which is confusing. This behavior of the system can be seen from 00:00:01 till 10AM (Exactly 10hrs UTC Time). After this time, dates are derived and updated correctly in the database. Looks like at some stage system is taking system time and converting into UTC time (10hrs behind our time)
I am not sure it is do with Support Pack or some other reasons.
Regards
KK

N560GTX-Ti Twin Frozr II/OC latest bios to solve TDR issue

Please help with getting latest bios, to prevent TDR issue.
S/N: 602-V238-130B1103124781
Current BIOS h**p://dump.ru/file/5741224

your vbios is latest version

Issues solved after a second install of Belle

Hi.
I have been advised to reinstall Belle on my Nokia E7.
I've been told that after a second install of Belle most issues are gone.
Do you know what specific issues are solved after that reinstall?
I'm curious because I want to know if it is worthy to reinstall Belle.
Greetings from Paraguay.
Claudio Bogado Pompa.
Greetings from Paraguay.
Claudio Bogado Pompa.
Solved!
Go to Solution.

Claudio,
I upgraded from Anna to Belle on the first day that Belle was available. Yesterday I re-installed Belle.
Since updating my E7 from Anna to Belle I have had mixed opinions as to whether that was wise to do.
Though Belle has a lot to like about it in features and speed, there are many things that were really good in Anna but have been degraded or are even missing in Belle. See this list which many people have contributed to:
/t5/Software-Updates/List-of-Belle-additions-corrections-needed/td-p/1328167/page/3
I have customized the home screens (use three) quite a bit and have added a number of free apps for more convenience in use of the phone.
Before I tell you my experiences and give you my reasoning I should give some background about myself and my Nokia E7-00. Note that though I am very competent with computer hardware and software I have much less knowledge and skill with cell phones.
My E7-00 is my second Nokia phone experience. I also bought an E6-00 for my wife. I got the E7 for myself because I need the large keyboard for my large fingers and I like the GPS/maps capability. I got the E6 for my wife because she was unhappy with the touch screen on her Nokia 5230 and is more comfortable with a keyboard.
I have owned my E7 for less than a year, use it primarily for my small business, and upgraded to Anna immediately after purchasing it. Though I tested using a data connection for WEB browsing for a couple of months I don't subscribe to a data service now because I found little use for it and it is (in my opinion) very expensive here in Canada. I do connect my E7 to the Internet often using WIFI through my home or business routers, and occasionally through WIFI connections at hotels and other locations when I travel.
Since upgrading to Belle I have had many occasions when my phone would freeze either momentarily or permanently (necessitating powering it off) and a few times it has completely shut off for no reason. I have had a number of occasions when I have been unable to answer an incoming call because the touch screen was unresponsive.
In trying to determine the cause of the problems with the phone I have removed apps and done soft resets of the phone.
I thought about re-installing Belle but was loath to do it because of the bad experience I had when I first upgraded from Anna to Belle. At that time I did a backup of my phone using the latest version of Nokia Suite. The download and install of the Belle update went very smoothly. But once the phone was functional again I found that I lost many things including all my customizations, my WIFI settings, and all the many map favorites (GPS coordinates) I had collected when traveling and calling on customers. The backup that the Belle installation software performed did not restore these things, and the same was true of the backup I did with Nokia Suite.
Yesterday my frustration level with the phone was such that I decided I had to try a re-install of Belle. I did another backup up the phone with Nokia Suite and synced the map favorites with Nokia's on-line service. But I also had the inspiration to download the latest version of Nokia PC Suite and do a backup with that too - a good thing I did!
I used Nokia Suite to re-install Belle. After the reinstall I again had lost all my customization, some installed apps, and all map favorites. I tried to restore things by using the backup I had done with Nokia Suite, but that did not work.
Then I restored the backup I made with Nokia PC Suite and EVERYTHING was back. I could hardly believe my good fortune. Even my map favorites were back.
Since it is little more than 24 hours since my re-install of Belle I cannot say whether it was really worth the effort. But so far the phone does seem to be behaving itself. It is a little smoother in operation with less delay and I have not had any freezing. On the other hand it has been a quiet day and the phone has not had a good workout. Still, I am hopeful.
This most recent experience makes me wonder if Nokia is making improvements in Belle without giving notification. I am wondering if the version of Belle that was used for the re-install is different from the original version I installed about a month ago.
I will not upgrade my wife's E6 to Belle until I know that the problems with Belle have been fixed.
I hope you find this information useful.

Latest update issues

Since downloading the latest update I have been experiencing these issues:
Calendar events take a few seconds to upload. All events disappear, then reappear.
Often loose connection to cellular network. Only solution is power off and restart phone. Never experienced this before.
Predictive text is now too predictive- even when spelling words correctly, after hitting space bar word gets changed.
The most frustrating is losing network connection. I will have full bars signal, but no 3G or e. Cannot receive/make calls, texts or email while the phone is in this state. Happens all the time with no apparent cause.
When I uploaded the new software, I did a reset for my phone. Returned it to its factory settings and did not upload the backup.
Is this Apple's way to force their new iPhone 4 on me?
It would be more frustrating surely given its antenae issues...

Well, I went to the Apple store and they gave me a new phone. I had asked for one that did not have the latest update after hearing from the floor staff that the 3G phones were experiencing problems with the update.
They couldn't find one without the latest update, but they assured me it should solve the issues with Calendar and "cannot activate cellular network" and once Apple releases another update, I should be golden.
The issues promptly started again while I was standing outside of the store.
Then, last night I see the 4.1 update had been released. I downloaded it.
No dice.
Please, Apple make your updates work for your products.
Why not just create updates for model?

Photoshop CS6 - 64 bit Optimus issue - SOLVED!

Photoshop CS6 64-bit will not run when Optimus is enabled on my W520 system The program works fine if I have discrete only set in the BIOS. Setting the default graphics adapter to NVIDIA GPU when using Optimus still has the problem. Anyone seen this issue before? CS6 Photoshop 32-bit runs OK under Optimus with the NVIDIA GPU set as default. I'm stumped so far. I searched the Adobe Support site and found nothing concerning this issue.
Update_1: I initially installed the latest NVIDIA driver from the W520 Driver Matrix. The NVIDIA level downleveled from 296.88 to 296.20, but CS6 started working properly. I then downloaded the latest NVIDIA driver 301.42 which was the level recommended by several graphics sites. The system is working smoothly now. CS6 will now use the OpenGL and acceleration features of the 2000M. BTW, my WEI changed from 6.5 to 6.6 with this driver. The 3D graphics still remains at 6.9.
Update_2: I encountered yet another anomaly with the display driver. I placed the system into Discrete Graphics and updated the display driver to 301.42. When I set the system back to Optimus, the CS6 programs could no longer access the NVIDIA GPU. I had to reinstall the 301.42 drivers again in Optimus mode to have everything back to full function. I switched back to Discrete mode to check if things were still working (they were) and then I returned to Optimus mode and the programs continued to function properly. There must be a sequence that requires Discrete updates first, and them=n Optimus, but I've never seen it documented.
W520, i7-2820QM, BIOS 1.42, 1920x1080 FHD, 32 GB RAM, 2000M NVIDIA GPU, Samsung 850 Pro 1TB SSD, Crucial M550 mSata 512GB, WD 2TB USB 3.0, eSata Plextor PX-LB950UE BluRay
W520, i7-2760QM, BIOS 1.42 1920x1080 FHD, 32 GB RAM, 1000M NVIDIA GPU, Crucial M500 480GB mSata SSD, Hitachi 500GB HDD, WD 2TB USB 3.0
Solved!
Go to Solution.

Thanks for tip!!!
Community Advocate Program Manager
English Community Deutsche Community Comunidad en Español Русскоязычное Сообщество

FIX: FireWire communication issue solved - What worked for me

After installing the iPod Updater 2006-01-10, I found that my FireWire devices (not just my iPod) no longer worked. After much messing about with all the suggestions I found online (none of which worked) I've managed to sort out the FireWire communication issues I had.
you can read about the exact issues I had here:
http://forums.kustompcs.co.uk/showthread.php?t=35034
and here:
http://discussions.apple.com/message.jspa?messageID=1562072
Unfortunately those looking for a quick fix will be disappointed, I had to:
a) Send my iPod Mini back to Apple, which was promptly replaced
b) Totally re-install Windows (including drive format)
c) Borrow the install CD that came with my friends iPod, which had a later version of iPod Updater (2005-10-12) than the one I had on my install CD, but earlier than the dreaded 2006-01-10
If anyone needs this updater (as it's impossible to find an earlier one on Apple's website) drop me your email in here and I'll send you the web address to download it. This is basically a ZIP of the original CD, totally virus free (for those that are worried) and appears to work fine.
If Apple have an issue with this, then why don't you fix the link on your site to this updater; this is simply my response to the complete lack of response from Apple on this matter.
A quick note about the: 'connection rate=S100 ERROR'.
If you discover you have this error when you test your iPod in diagnostic mode; find out how to do this here:
http://www.methodshop.com/mp3/ipodsupport/diagnosticmode/index.shtml
Then it appears there is nothing you can do to fix this other than sending it back to Apple. No amount of restoring will solve it.
I hope this helps someone out there! I've yet to fix the issue with my LaCie drive (basically it needs sending back) which if anything proves that whatever screwed my system did something to the hardware on a low level, it wasn't a Windows software issue, because after re-installing it, I download SP2 and ALL the latest hotfixes, if that was the cause, it would have done it again.
This leaves one culprit - the iPod Updater 2006-01-10, as this was the only software I installed at the time both of my FireWire devices went down, avoid it like the plaque.
Regards
Matt

After installing the iPod Updater 2006-01-10, I found that my FireWire devices (not just my iPod) no longer worked. After much messing about with all the suggestions I found online (none of which worked) I've managed to sort out the FireWire communication issues I had.
you can read about the exact issues I had here:
http://forums.kustompcs.co.uk/showthread.php?t=35034
and here:
http://discussions.apple.com/message.jspa?messageID=1562072
Unfortunately those looking for a quick fix will be disappointed, I had to:
a) Send my iPod Mini back to Apple, which was promptly replaced
b) Totally re-install Windows (including drive format)
c) Borrow the install CD that came with my friends iPod, which had a later version of iPod Updater (2005-10-12) than the one I had on my install CD, but earlier than the dreaded 2006-01-10
If anyone needs this updater (as it's impossible to find an earlier one on Apple's website) drop me your email in here and I'll send you the web address to download it. This is basically a ZIP of the original CD, totally virus free (for those that are worried) and appears to work fine.
If Apple have an issue with this, then why don't you fix the link on your site to this updater; this is simply my response to the complete lack of response from Apple on this matter.
A quick note about the: 'connection rate=S100 ERROR'.
If you discover you have this error when you test your iPod in diagnostic mode; find out how to do this here:
http://www.methodshop.com/mp3/ipodsupport/diagnosticmode/index.shtml
Then it appears there is nothing you can do to fix this other than sending it back to Apple. No amount of restoring will solve it.
I hope this helps someone out there! I've yet to fix the issue with my LaCie drive (basically it needs sending back) which if anything proves that whatever screwed my system did something to the hardware on a low level, it wasn't a Windows software issue, because after re-installing it, I download SP2 and ALL the latest hotfixes, if that was the cause, it would have done it again.
This leaves one culprit - the iPod Updater 2006-01-10, as this was the only software I installed at the time both of my FireWire devices went down, avoid it like the plaque.
Regards
Matt

Ralink RT3290 802.11bgn Wifi Card - Possible Issues [SOLVED]

Dear Lucky owners of such a card, At least from my experience I realized it is not that bad card, even if most probably many production pieces were faulty or not working properly, and many issues can be resolved. Let me list in order of time the issues I faced and solved about this wifi card: 0) First issue is not about RT3290 card itself but it is related to 802.11w encryption compatibility in between Windows8 and Cisco not allowing 802.11n speed rates so failing to G speeds only. - SOLUTIONS: a. As first test I would recommend trying another router from different brand to see if connecting at 802.11n speed rates b. If you prove point a issue, then try to fix the issue based on following post (in which you can see the reply from myself Emanuele on the 29th of Nov 2014): https://supportforums.cisco.com/document/113836/windows-8-clients-cant-associate-cisco-unified-wireless 1) Signal strenght issue: original wifi card RT3290 installed on my HP laptop was having really bad antenna, with signal fluctuating and sometimes bad even really close to any Router I tried. - SOLUTION: Replace the RT3290 card even with same new card. (In my case as laptop was under warranty, I proved the issue via screenshots and they replaced with new card solving my signal strenght issue). 2) Original issue (1) was actually resolved after HP replaced the wifi card with same model, but with the latest driver installed 5.0.45 seems like wifi rates change too frequently based on high sensitivity of the driver itself, so that suggested me issue was still there, so making me re-testing anything from scratch. - SOLUTION: Install 5.0.37 Driver - frequent rate changes issue (with driver 5.0.45) disappears and sensitivity of signal to rate changes seems to be a really good compromise to have good throughput. 3) To check out 2nd issue above I started again using a third party software inSSIDer free version to check signal while I was doing speedtest on web.
- RESOLUTION:
inSSIDer normally works on Windows7 without any issue but on Windows8 (at least tested with RT3290) I have just discovered somehow this software was slowing down wifi card performance drastically showing a speed up to 0.1Mbps rather than 40Mbps. Simply closing the application issue was not recurring, so uninstalled it and after solving all the other issues above this card works perfectly (at least so far ) Hope this post will be informative and will help other about-to-get-mad guys as me

Hye. After I read up your solutions, I am quite impressive and really want to try out those solutions. However, I am not very computer wise and I really appreciate if you make a video on solving this problem. Up to you if you want to upload it on the youtube (so that others with similar problem can view it and solve the problem too) or you want to direct email to me ( [email protected] ). I really hope you can help me because I am stuck with this problem since last year. Thank you!!!

Error -50 + HDD issues [Solved]

Hello!
I want to share some issues that I've had with my Macbook pro, which I've now solved, and I hope it can help others experiencing the same issue. Alright, first an overview of my problem (you can read the summary at the end of the text to skip the details):
Problem History:
I have a Macbook pro medio 2009 15", 2,53 gb HDD. My Macbook worked just fine until about 4 months ago. While working on my mac, suddenly I could'nt delete or download any files and an "error: -50" showed up. Then, I rebooted my mac and several things happened. In the first 5 or so reboots I could log into my account but the -50 error was still there - meaning I couldn't use "finder" properly and basically no applications. Then, after a while, my mac couldn't start up - it showed only a white screen loading and never moved on. So, I put the mac into recovery mode, which worked after several times and diagnosed my harddisk drive and the diagnosis showed a normal functioning harddisk. I wasn't able to run a hardware test for unclear reasons. After several tries, I installed Mountain Lion OSX (had Lion before) through the harddisk recovery mode and my mac worked fine - until 9-10 hours later where the same issues mentioned above arose anew. Now, I did not have any access to my mac at all - besides the harddisk repair mode (Don't remember the exact name of it), which was usel
Now here's what I did:
1: I bought a new Harddisk drive and replaced it - that didn't work out!
2: I bought an external harddisk drive connector. Meaning, my internal harddisk worked as an external harddrive and I ran my OS through USB. I booted my mac holding "option" until it showed the harddrive. And it worked! - Although my mac became slower.
3: Even though my mac worked fine now - it was annoying having to carry an external drive all the time and holding the option button every time etc. etc. So, I figured that the problem is either with the logic board or the harddisk connecting cable. The logic board is the last thing one must rule out - because if it is faulty - you're kind of screwed. So, I went ahead and ordered a connecting cable (approximately 60$). The cable was faulty and didn't work! I returned it and got a new one instead (same company and same quality) - and now my mac is working again!!!
Summary:
1. Had error -50 and harddrive issues; couldn't delete, download or even use any apps or files.
2. Mac wouldn't start up.
3. Tried disk repair + fresh OSX install. Did'nt work
4. Replaced harddisk - didn't work.
5. Replaced Harddisk connecting cable: PROBLEM SOLVED!
A piece of advice:
If you have any problems, then try to test one thing at a time. Run a hardware test from apple or other sources. Have an expert checking your mac - it might cost a little but it's worth it if you find out what the problem is. Buy quality parts for your mac if you have the money (I bought a cheap connecting cable :/ ).
And lastly: I hope this was helpful to other mac users!
Have a great day/evening/night!
- MS

THANK YOU. Saved me a few hours, this did.
This is stil not fixed in the latest iTunes, MobileSync, or iOS 6. Whichever piece has the problem is still badly broken, and in this age of 64 GB flash drives in MacBook Air models, surely we're not the only two that have moved that monstrous folder out to an external drive....

Front row in Lion 10.7 issue (-70012) and video_ts not playing issue -solved

Hi all,
thought I just post my solution to the front row issues in 10.7. I looked for a solution for days, and when I found it, I thought it would make other peoples live easier if I combine everything in one post.
I actually had a couple of issues:
PROBLEM:
first front row stopped playing VIDEO_TS files in 10.6.
the second issue occurred when I thought upgrading to 10.7 would solve the issue; Front row still couldn't play the VIDEO_TS, because FRONT ROW was gone...
SYMPTOMS:
both issues always showed the same symptoms:
when a dvd-back folder was selected, front row would show a black screen, and then, caused by my frantic pushing the ESC button, front row would give me the dvd player not valid -70012 error.
CAUSE:
so what happened? I chose to buy my MBP 17" with the smallest HDD (yep sorry, was cheap-s-ing). Then later that year, I decided to buy the HDD caddy and switch my internal superdrive for a SSD. I ended up placing the original HDD in the hdd caddy, which I then put in the Superdrive's slot, and I placed the SSD in the slot where the original HDD was residing first. I now had a MBP 17" late 2011, with vertex3 SSD. I forgot, I also put in 16 GB, replacing the 8 GB.
So, when I back-upped all my favorite DVDs as VIDEO_TS files, (no I did not download dvds through usenet), grabbed the popcorn, and started Front Row, the disappointment began. No VIDEO_TS file would play, always the same -70012 error message. So after a lot of internet research I stumbled upon a guy who said: yeah, you have to upgrade to 10.7. After the upgrade my FRONT ROW was gone.
SOLUTIONS:
In 10.6:
As Apple's DVD player is always looking for the internal dvd player as a prerequisite to start, Front Row, which uses Apple's DVD player as video player, will throw up the -70012 error. 'Cause it finds the HDD in the HDD Caddy instead of the SuperDrive. So in 10.6 (and in 10.7 also) you can use the following solution:
(I got this solution partial from http://reviews.cnet.com/8301-13727_7-20070591-263.html)
1: modify the DVDPlayback framework that the DVD Player uses so that it will recognize external drive as a valid DVD playback device. (The HDD Caddy came with an external casing for the SuperDrive)
2: download a hex editor (I used Hexedit 220 from http://hexedit.sourceforge.net/ )
3: Go to the folder /System/Library/Frameworks/ and back up the file "DVDPlayback.framework."
4: Open Hexedit_220 and use it to open the following file:/System/Library/Frameworks/DVDPlayback.framework/Versions/A/DVDPlayback.
5: Using the editor's find&replace through COMMAND-F, replace "Internal" with the text "External" and save the file. Note that Hexedit also saves a backup automatically.
6: Close the file once saved, and then run a permissions fix on the boot drive using Disk Utility. Then restart the system and you should now be able to play DVDs off the external drive using DVD Player. That is, If you use an external dvd player (which I don't use).
7: I inserted a very small USB stick in the MBP with no data on it, and Front Row and Apple DVD Player accepted this. I could now play my backupped DVDs.
ofcourse, I still wanted to upgrade to 10.7, so here's the solution to 10.7
10.7:
upgrading was a simple click with the mouse, worked like a charm, Office still worked, and some minor updates installed through software.
Front Row however, gone...
I used the steps outlined in http://osxdaily.com/2011/07/21/front-row-for-mac-os-x-lion/ to get Front Row back:
- first get the package from Madhatter: Download the free package installer by MacHatter
- install, or customize the install
- all done.
Then I used the steps from step 3 through 7 outlined above in solution 10.6.
Catch:
So I did not find a solution to fooling the DVD Player / Front Row with the USB stick. So everytime I watch VIDEO_TS in Front Row the USB stick must be inserted. But, the good news, I can still use my remote control for something.
Hope I helped some guys out there with this solution.
Regards,
Johnno

The issue has previously hit Apple TV owners. I think people came to the conclusion that it was a HDMI handshake problem. Basically the process where the device and TV greet each other, make up some rules about communicationg and what their secret key is and so on.
I haven't tried this yet, but my local service center says that basically I can do one of two things:
- Downgrade to 10.7 and then download the 10.7.1 update from Apples website. To do this without having a Mac OS X Lion disc, you can hold down CMD + R when the computer boots to be able to access the recovery partition on newer Macs that come without the OS disc.
or..
- Put something in between the computer and TV. For example, if you're using an amplifier as a part of your home theather set up, this will probably work. The service guy said he has his Mini connected to the amplifier, which in turn is connected to speakers and a projector. The inverted colors still appear, but only once per night (i.e. after the first problem is reset by resetting the link then it's fine).
For now, I'll do my little dance of changing the source on the TV from HDMI 1 to HDMI 2 and then back again to reset the link... But, I'll probably try downgrading in a few days.

Tecra A11 - Video/Latest BIOS issues

Hello All,
I just received a Toshiba Tecra A11 the other day which is out of warranty (Refurb). When I got the laptop there was an issue where the picture was displayed at 1024x768 and off centre (In BIOS). The image was 1-2cm off screen to the left, with about 5-6cm black space to the right of the picture, the bottom 2-3 cm's of the picture were also off the bottom of the screen.
I installed Ubuntu Studio initially and attempted to force the display to a widescreen resolution. I didn't have any luck, I also installed Win7 but still with the latest drivers I had no luck.
This was strange because BIOS was displayed the same way so naturally I decided to upgrade to the latest BIOS version. The BIOS on the laptop was quite old (End of 2009).
I downloaded the BIOS update from Toshiba's web site, and ran the update.
The new BIOS was installed and the machine rebooted.
However there was no picture displayed on the LCD panel, windows did successfully boot, if I connect an external monitor to the laptop I get picture. When starting the laptop the LCD backlight does light up.
My question is: What can I do to resolve this issue? Is there a BIOS recovery or downgrade tool available? Is it possible to reflash the bios? What is recommended?
Thanks.

> The new BIOS was installed and the machine rebooted.
> However there was no picture displayed on the LCD panel, windows did successfully boot, if I connect an external monitor to the laptop I get picture. When starting the laptop the LCD backlight does light up.
Does this mean that everything is ok using external monitor?
Can you access the BIOS pressing F2 and can you set it to default settings?
Usually you can switch between external and internal display using the key combination FN + F5. Does it work?

Latest wine issues[SOLVED]

Similar Messages

Maybe you are looking for