Go Back   DisplayLink Forum > DisplayLink Graphics Technology > Mac Software
Register FAQ Calendar Today's Posts Search

Reply
 
Thread Tools Search this Thread Display Modes
Old 03-31-2018, 05:17 PM   #1
Wozzy
Member
 
Join Date: Mar 2018
Posts: 58
Default

Quote:
Originally Posted by Kabrown View Post
Real simple question, how long till this is fixed? At present, you have a lot of users with money poured down a rathole until this is working again A time frame for solution would be good and would go miles from having this escalated to the FTC.
But is this Apples or DisplayLinks issue....or both.
Wozzy is offline   Reply With Quote
Old 03-31-2018, 07:45 PM   #2
DLguy
Junior Member
 
Join Date: Mar 2018
Posts: 11
Default

Both, apple ruined it for DL and DL needs to work on making updates to be compatible with the new OS
DLguy is offline   Reply With Quote
Old 04-01-2018, 08:49 PM   #3
bernie
Member
 
bernie's Avatar
 
Join Date: Jun 2010
Posts: 39
Default What if only Apple can fix it?

Quote:
Originally Posted by DLguy View Post
Both, apple ruined it for DL and DL needs to work on making updates to be compatible with the new OS
It may not be possible for DisplayLink to do anything if the problem is at the OS API level.

What if DisplayLink and the other affected companies simply have no ability to restore extended display support? What if only Apple can restore it to work as it did in 10.13.3?
bernie is offline   Reply With Quote
Old 04-01-2018, 10:39 PM   #4
tommiy
Member
 
Join Date: Mar 2018
Posts: 92
Default

Quote:
Originally Posted by bernie View Post
It may not be possible for DisplayLink to do anything if the problem is at the OS API level.

What if DisplayLink and the other affected companies simply have no ability to restore extended display support? What if only Apple can restore it to work as it did in 10.13.3?

Entirely possible and after 3 months of trying to get it to work with beta's and the requests from DisplayLink to log fault on the 10.13.4 release I would say that its in a position where only Apple can assist if they want to. If not then the use of MACs on this technology is history by the looks. I would have expected if it was possible after 3 months it would have already been done.

Time will tell but I guess that it depends on how generous Apple is wanting to be. I, myself, logged a fault and rolled back to 10.13.3.
tommiy is offline   Reply With Quote
Old 04-02-2018, 02:44 AM   #5
Alanant
Member
 
Join Date: Jan 2018
Posts: 31
Default

Unfortunately, this debacle is another example of the Apple Tax/Fanboy Fee. Our office is keeping pre-2017 Macs on 10.13.3 (spending hours reinstalling 10.13.3 on the ones that have already upgraded). For thunderbolt three capable Macs we are looking at purchasing non-DisplayLink docks for several hundred dollars apiece. Not sure what we will do with the pre-2017 10.13.3 Macs when the next security-related vulnerability hits...
Alanant is offline   Reply With Quote
Old 04-02-2018, 11:53 AM   #6
Teledatageek
Junior Member
 
Join Date: Apr 2018
Posts: 2
Default

Quote:
Originally Posted by Alanant View Post
Unfortunately, this debacle is another example of the Apple Tax/Fanboy Fee. Our office is keeping pre-2017 Macs on 10.13.3 (spending hours reinstalling 10.13.3 on the ones that have already upgraded). For thunderbolt three capable Macs we are looking at purchasing non-DisplayLink docks for several hundred dollars apiece. Not sure what we will do with the pre-2017 10.13.3 Macs when the next security-related vulnerability hits...
Having just purchased a couple of USB-C docks from Startech, this makes me very unhappy.

Two questions:

1. What non-DisplayLink docks are you looking at? I need to drive two monitors and haven't found a non-DisplayLink dock that does that.

2. This is an opinion question - but if Apple doesn't ever fix this or it drags on like it already has - should the dock manufacutuers provide a refund since the product is not performing as advertised? Personally, I think so. Sure, they can blame Apple, DisplayLink, etc. but in the end they sold a product that relied on that technology...

Thanks!
Teledatageek is offline   Reply With Quote
Old 04-02-2018, 02:03 PM   #7
chops
Junior Member
 
Join Date: Apr 2018
Posts: 1
Default

Quote:
Originally Posted by Alanant View Post
Unfortunately, this debacle is another example of the Apple Tax/Fanboy Fee. Our office is keeping pre-2017 Macs on 10.13.3 (spending hours reinstalling 10.13.3 on the ones that have already upgraded). For thunderbolt three capable Macs we are looking at purchasing non-DisplayLink docks for several hundred dollars apiece. Not sure what we will do with the pre-2017 10.13.3 Macs when the next security-related vulnerability hits...
May I ask how you rolled back? I spent hours and ended up going back to 10.12.6 since I couldn’t find a way to install only 10.13.3. I do not have Time Machine backups.
chops is offline   Reply With Quote
Old 04-02-2018, 02:37 PM   #8
Alanant
Member
 
Join Date: Jan 2018
Posts: 31
Default

Quote:
Originally Posted by chops View Post
May I ask how you rolled back? I spent hours and ended up going back to 10.12.6 since I couldn’t find a way to install only 10.13.3. I do not have Time Machine backups.
You can only easily reinstall the version that your Mac came with (I guess 10.12.6 in your case).

We have the 10.13 5.2 GB DMG file from when it first came out. You might be able to find it on the internet. Once it was installed, I installed the 10.13.3 Combo update which is still hosted by Apple.
Alanant is offline   Reply With Quote
Old 04-02-2018, 05:26 AM   #9
Alanant
Member
 
Join Date: Jan 2018
Posts: 31
Default

Quote:
Originally Posted by tommiy View Post
Entirely possible and after 3 months of trying to get it to work with beta's and the requests from DisplayLink to log fault on the 10.13.4 release I would say that its in a position where only Apple can assist if they want to. If not then the use of MACs on this technology is history by the looks. I would have expected if it was possible after 3 months it would have already been done.

Time will tell but I guess that it depends on how generous Apple is wanting to be. I, myself, logged a fault and rolled back to 10.13.3.
I agree, Apple are not going to fix this.
Alanant is offline   Reply With Quote
Reply


Posting Rules
You may not post new threads
You may not post replies
You may not post attachments
You may not edit your posts

BB code is On
Smilies are On
[IMG] code is On
HTML code is Off

Forum Jump


All times are GMT. The time now is 10:54 AM.


Powered by vBulletin® Version 3.8.7
Copyright ©2000 - 2026, vBulletin Solutions, Inc.