Moravian ASCOM fail

[DaveS]

With gobbledegook

I suppose this means something to geeks, but is meaningless gobbledegook to me.

All I know is that I had the camera working and would connect to Maxim when I bought the bloody thing but now this.

I've downloaded the bloody drivers and installed them, so I don't know anymore.

Might sell up and be done with it.

 

[tomato]

I'm no geek but there is an error code 80040154 embedded in the gobbledegook. I googled this and found a possible Microsoft fix:

https://mslivehelp.com/windows-update-error-80040154-10-8-7/

[DaveS]

OK, I solved the problem by reading closely the PDF that came with the driver, only really possible when I had it on the big screen of the office computer, instead of the laptop I was using in the obsy for RDP.

Turned out I had downloaded 64 bit drivers, while Maxim needed 32 bit ones. Given I had Win10 64 bit, a natural mistake to make.

But why the bloody hell couldn't it have said something like "Oops, the drivers are 64 bit but I need 32 bit"? Instead of ininteligible gobbledegook. I could have fixed it in 5 mins instead of pulling my hair out and nearly taking a sledgehammer to the whole shebang.

[Davey-T]

4 minutes ago, DaveS said:

But why the bloody hell couldn't it have said something like "Oops, the drivers are 64 bit but I need 32 bit"? Instead of ininteligible gobbledegook

Tried to unzip a big folder yesterday and got similar long rambling message about unable to create folder gobbledy , gobbledy, goobledy etc etc, turned out there wasn't quite enough disc space to create a temp folder so why the hell couldn't it just say that and why didn't it check first ?

Dave

[DaveS]

Written by geeks for geeks. Same as always.