|
09-25-2009, 03:45 PM | #1 |
Junior Member
Join Date: Sep 2009
Posts: 1
|
Windows Server 2008 R2 support
I noticed that the RC and Beta 2 are blocked on Windows Server 2008 R2 (X64). When I attempt to install, a message is displayed, "The software for DisplayLink Graphics is not supported on this operating system version. Please visit www.displaylink.com/software for an updated driver."
I realise that the configuration may not be supported, however:
Last edited by merlyn; 09-25-2009 at 06:32 PM. Reason: Correcting: Previous OS (oops). I have it right this time. |
10-01-2009, 09:53 PM | #2 |
Junior Member
Join Date: Oct 2009
Posts: 4
|
I agree. The first beta supported Windows Server 2008 R2 and now I'm stuck 3 beta drivers behind and it's bad too because of the slowness and the speed of window refreshed that have been fixed in the later beta's in fixed in Windows 7.
Please please please fix this or provide a work around for power users who need the 3 monitors and utilize a power workstation / server as a monitoring station. I'm almost to the point where I'm going to buy another video card and sell the dock because if it's not going to be supported then this solution won't work for me. Please give us an update on this. |
10-08-2009, 05:38 AM | #3 |
Junior Member
Join Date: Oct 2009
Posts: 1
|
I just purchased a Mimo and I'm very disappointed to find out that I couldn't run it on 2008R2 or 2003 (32bit).
I can understand the reason for not supporting an OS (dev time, testing, etc.) but please don't block the install. It would be nice just to have a pop-up that says "Hey this is unsupported OS. Do you want to continue?" I can't see any reason to block 2008R2 it's just Win7 with server licensing even the build numbers are the same. Please. At least remove the block and sign the driver for R2. |
10-08-2009, 01:41 PM | #4 | |
Junior Member
Join Date: Oct 2009
Posts: 4
|
Quote:
As a tip you can download the very first beta and it does work on R2 but it's slow and buggy with screen refresh on my setup. Dunno if it's an Aero thing or not but it takes sometimes 4 to 5 seconds to switch between windows and this is on a fast Raid 0, Quad core machine. Again we've had almost 100 views and 3 ppl post. I'm certain this is a larger problem than most are even posting and we've yet to see anything from the Display link staff even noting that we exist. If we don't get an answer in the next week or so I'm returning mine for a full refund at Sam's. That is where I bought it and I'll just buy a different solutions. It's a real shame this solution and our questions go unsupported and unanswered for so long. I'm sure we are going to get a post that says "IT'S BETA YOU IDIOT" and I totally understand that it is but having 0 communication with the dev team is also unacceptable too. Especially if they have this forum for communication and feedback for issues. Last edited by prologix; 10-08-2009 at 01:43 PM. |
|
10-13-2009, 05:26 PM | #5 |
Junior Member
Join Date: Oct 2009
Posts: 18
|
Is there now a way to use it in Server 2008 R2 64Bit ?
It says Unsupportet OS Please DisplayLink Support Team Help |
10-13-2009, 09:21 PM | #6 |
Junior Member
Join Date: Oct 2009
Posts: 2
|
Need Win2008 R2 X64
I join the above thread. Note that some software companies are using Windows Server 2008 X64 as their main desktop to run Hyper-V. If you do not support this OS, they will not be able to use DisplayLink-certified hardware to add monitors to their desktop.
Indeed, B1 driver works fine. We all want to enjoy from latest improvements, please do not completely block setup or at least enable command line switch to unblock it. |
11-06-2009, 07:34 PM | #7 |
Junior Member
Join Date: Nov 2009
Posts: 2
|
Solved? :-)
Hello ladies and gentlemen!
It seems I figured out a little workaround: I had the problem on Win2003 server. You'll wonder: After getting the same error about my OS, i tried to start setup in compatibility mode (right-klick, properties, compatibility). WinXP-Mode didn't work, but Win2k did! I'm running my MiMo 720 on Win2003 server now. Greetings, Steuk |
11-06-2009, 11:16 PM | #8 |
Junior Member
Join Date: Nov 2009
Posts: 2
|
not quite yet :-/
Greetings. It seems I started yodeling too early - it doesn't work as I wish.
Exactly: After started in "win2k-mode", the driver has been installed and a 2nd monitor is listed in the display properties. Nevertheless, device manager lists a monitor named "none" (uh, there is a no-device plugged in. greetings from nietzsche!) and resolution of this none-monitor has only default values of eg. 640x480; correct resolution is not listed. This all wouldn't matter. BUT, ladies and gentlemen, the worst thing with this: The f....g device doesn't display anything! Allright, so I don't have a sollution, too. But maybe this could be an approach for someone of you. I'd be lucky to hear about! |
11-07-2009, 08:21 AM | #9 | |
Junior Member
Join Date: Oct 2009
Posts: 18
|
Quote:
|
|
11-09-2009, 05:49 PM | #10 |
Junior Member
Join Date: Nov 2009
Posts: 2
|
Unbelievable!!!!!!
When will this be fixed? There has to be a workaround; this is ridiculous.
I tried installing the package in a Win7 VM and moving the drivers back over to the server (along with several variations along that line), but to no avail. The architecture of the product doesn't appear to be straightforward enough for that. I hadn't been able to find an add-in card that would give me a 3rd display port that works with my onboard VGA/DVI combo. Your USB adapter technology was the only one I'd been able to find that would allow them to coexist. I've now lost my 3rd monitor - again. This is unacceptable. I now see that I'm not the only person experiencing this issue. If this is Microsoft you're fighting with, they should know they have tens of thousands of developers that use their server products for development. I am a legitimate user of 2008 R2 server; I downloaded and installed it as part of the Microsoft Gold Partner program. If it's not Microsoft you're fighting with, then what's the use of your patent? Please advise on my options and/or a timetable for resolution ASAP. |
|
|