In a brief departure from sanity, I recently thought to myself, “surely ZoomText must be better than it once was, I’ll try it again!”

I downloaded on my laptop, looks relatively good. I download it on my desktop, I download it on my desktop, everything just looks blurry/squiggly.

So I called tech support, to see if they can help me sort this out before I buy the app.

Highlights from the call have included, but are not limited to:

“The clarity of the text depends on the website, what font they use. As it gets bigger it’s going to get blurry.”

When I explain that zoomtext hooks into, like, the actual text in the apps it can (which I don’t actually know the technical term for, lol) tech support guy informs me that he doesn’t think that’s how the app works. (That it’s all just, like, interpolation like zooming into a digital photo.) EDIT: I subsequently found out that they have been having issues with the “xFont” feature for years now.

Dude wants to make a registry edit. Bold move, tier 1 tech support bro, but it just looks like a font change, probably not going to brick anything.

Taskbar no longer functions correctly after reboot, even with Zoomtext off. He scrolls aimlessly in the registry before going into Zoomtext and trying to make changes that have absolutely no relation.

I pointed this out. He told me he knows. He proceeds to try to make changes in zoomtext repeatedly anyways.

He then informs me that he’s waiting for his colleague for help.

When I ask if this can be escalated above tier 1, as I rather would like them to unbrick it, he tells me “he’s the one who gave us the change.” Okay, that does not inspire confidence…

At one point, he told me to “calm down.”

When I asked him to just email me over the changes he made, he tells me “you’re looking at it.” I was not, in fact, looking at it.

We are now on hold for his “colleague,” or at least for him to furiously google registry changes how to revert or something.

In addition to the above bricking, the text in zoomtext is just as blurry as it was. 😂

Update: after he failed to solve the problem, he tells me that although it’s “hard to believe,” the registry edit had nothing to do with an immediate problem upon reboot, and they’re totally unrelated and there’s nothing he can do. But don’t worry, he’s going to forward my contact info to management!

Update 2: I fixed the problem a couple of minutes off the call by, shockingly, reverting the change he made to the registry.

Update 3: to their credit, a manager and supervisor called me just now. They expressed concern over the support I received during the call, and were ready to help me fix the registry issue, which was thankfully already resolved. I outlined the troubleshooting steps I’ve taken, they agreed that I tried all the easy fixes, and said that the person to talk to was someone with much more Ai Squared/Zoomtext knowledge to their Freedom Scientific/JAWS knowledge, who was out on vacation and could call me next week. Overall the people I spoke with seemed fairly competent and helpful. They sent me over a 90 day trial code (versus running in 40 minute mode) to troubleshoot the problem. While they didn’t have an immediate solution to my issues with Zoomtext, I appreciated both their willingness to follow up on the issue as well as their acknowledgement that a mistake had been made by the previous person I spoke with.

10/10 experience all around.

    • shacklebolt@rblind.comOP
      link
      fedilink
      English
      arrow-up
      3
      ·
      9 months ago

      Not as far as I’m aware of. Window’s built in magnifier has greatly improved over the years however, it used to be very poor quality at bigger sizes. But the windows magnifier has gotten better and is very functional, and if FS can’t deliver on Zoomtext’s big selling point (crystal clear “xFont” texts), then zoomtext has gotten worse.

        • shacklebolt@rblind.comOP
          link
          fedilink
          English
          arrow-up
          2
          ·
          edit-2
          9 months ago

          The edit he made was weird, though. This is what he ran:

          Windows Registry Editor Version 5.00 [HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\Windows NT\CurrentVersion\Fonts] “Segoe UI (TrueType)”=“” “Segoe UI Bold (TrueType)”=“” “Segoe UI Bold Italic (TrueType)”=“” “Segoe UI Italic (TrueType)”=“” “Segoe UI Light (TrueType)”=“” “Segoe UI Semibold (TrueType)”=“” “Segoe UI Symbol (TrueType)”=“” HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\Windows NT\CurrentVersion\FontSubstitutes] “Segoe UI”=“Myanmar Text”

          I resolved the problem simply by changing the last line to:

          “Segoe UI”=-

          That resolved the issue with my taskbar.

          But I have no idea why he thought his edit would fix my problem. I’m not entirely sure he had any idea why he thought it would, either.

          He didn’t do anything to resolve the issue with Zoomtext not working properly, that remains outstanding, not that I’m feeling super inclined to keep trying.

          I’m running a 12700k with a 3080ti, more than capable of running Zoomtext.

          I tried:

          • Upgrading from Windows 10 to Windows 11 so as to match my laptop, on the chance there was some sort of win10 issue.
          • Reinstalling my graphics drivers, clean installs, tried both the “game” and “studio” versions, and tried an older release.
          • Looking to see if there was a Zoomtext device in my graphics devices, I thought that’s how it used to work, couldn’t find anything. (Reinstalled Zoomtext after this, nada.)
          • Unplugging my monitor from my GPU, plugging it into my motherboard, and changing the default display adapter to that.
          • Trying the “compatibility mode” display adapter in Zoomtext.
          • Installing a previous version of Zoomtext.

          Nothing. I honestly wouldn’t know where to start in troubleshooting beyond that.

  • pax@rblind.com
    link
    fedilink
    English
    arrow-up
    1
    ·
    9 months ago

    I had a fs representative who installed JAWS incorrectly on my machine once when I got a license so that wasn’t the wildest