SOLVED: Of course I figured this out shortly after posting. I'll post the reason for this rather strange problem for anyone who might encounter the same thing.
I accidentally set RDP to use "High 8-bit color". This is why I assumed high contrast was enabled. Because JAWS takes over the video card it couldn't handle the 8-bit color and thus the machine pulled the blue screen. I'm not sure who's to blame for this. Microsoft for putting 8-bit color in RDP to begin with or Freedom Scientific for having an application that can crash the machine in such a way. Either way, problem solved (don't use 8-bit color) On Monday, March 23, 2015 at 10:23:15 AM UTC-6, Tyler wrote: > > Hey Everybody, > > So I’m using Microsoft RDP for the Mac which has worked > surprisingly well considering it’s a Microsoft product running on apple > technology. I recently ran into a spectacularly interesting problem that > I’m wondering if anybody can shed some light on. One of my remote desktop > sessions was connecting to a Lady’s Machine, her machine was running JAWS > (at the time 14) and she had high-contrast turned on. Now obviously JAWS > doesn’t play well with remote sessions but that’s not really the problem. > > The first time I remoted into her machine everything went well, > there were no errors and I logged out. The second time when I remoted in to > her machine it got the “blue screen of death” and proceeded to crash and > restart. It’s also worth noting that a couple of weeks after I remoted in > the first time JAWS started acting up, apparently cutting out frequently. > Every since my second remote session I simply cannot remote into her > machine without it crashing and getting that infamous blue screen. > > Okay so it was time for her to get a new machine anyways, so we > ordered her a new computer (rather nice, HP, i7 processor etc…) and I > started setting it up. Now for reasons unrelated to this issue I usually > set up a machine remotely, even if it’s sitting in my office and this is > where life gets weird. We have everybody set up on an Active Directory > domain so in order to remote into the new machine I duplicated her old > Remote desktop profile and just changed the machine name to match the new > one I was setting up. > > Upon doing this I realized that her machine was in high-contrast. > I assumed it was some how tied into her AD profile. The machine ran fine, I > was able to set up everything as normal (installed office, the free version > of Window Eyes etc…). Then I installed JAWS 16 (the demo version from the > freedom scientific website). The moment JAWS ran for the first time her > brand new computer had the same blue screen and proceeded to crash and > restart. > > The first thing to mention is I’ve got other people on our network > who are running JAWS and have remoted into their machines using Mac RDP > without issue. The next thing is that a colleague of mine remoted in using > windows RDP without issue to BOTH machines mentioned in this email. > Eventually I solved the issue by deleting both RDP profiles and re-creating > them. I can now remote in to both machines without issue. > > So to sum up my questions does anybody have any clue how or why > this remote desktop profile on the Mac would crash the remote machine ONLY > when JAWS is running? These problems were inexplicably tied in with JAWS > (debateable whether high-contrast had an effect). We have enough JAWS users > on the network that it’s worth my time to try and track down this issue. -- You received this message because you are subscribed to the Google Groups "MacVisionaries" group. To unsubscribe from this group and stop receiving emails from it, send an email to [email protected]. To post to this group, send email to [email protected]. Visit this group at http://groups.google.com/group/macvisionaries. For more options, visit https://groups.google.com/d/optout.
