(Problems with that can cause ntdll.dll grif on a PC, although it tends to be a bit more dramatic than what you're seeing.) Try detaching peripherals and seeing if the crashes in iTunes and Starry Night go away when a particular peripheral is plugged in. Head to the manufacturer's website of any third-party components you have added to the PC to check for any updated firmware or drivers for that componentry.Ĭabling for any peripherals you have attached to the PC. Try checking through the "recommended" category too (if they have such a category). Head to the drivers and downloads page for your model at your PC manufacturer's website and check forĪny important/critical updates relevant to your configuration. Because the ntdll.dll is such a basic part of the interface between the kernel and the devices and drivers, we'd better check on *absolutely everything* which can have a driver/firmware. So we'd probably better doublecheck your drivers/BIOS/firmware etc. (That has me wondering if there's actually a 32-bit version of a driver somewhere on your system that is getting in the way of quicktime doing something still-image/video related.) Does Picture Viewer crash?)ģ2-bit version of ntdll. Does the little menu bar for Picture Viewer come up? If so, try going "File > Open" and opening the "Sample" image. Navigate to C:\Program Files (x86)\QuickTime\ and doubleclick PictureViewer. (Plausibly, you might be able to check on that using Picture Viewer. and if there's an issue with the visual display capabilities of your QuickTime on PC, that would probably cause grief when the QuickTime Player tries to launch under default conditions. By default, QuickTime Player will try to bring up the content guide on launch. My guess is that something similar to that is happening when you launch QuickTime. It's only when it performs certain functions, like displaying video in iTunes that we get the crash. ![]() QuickTime player *is working to some extent* on your PC. I think we're probably looking at some subtle device or drivers issue. Both MaximDL and Starry Night should now have combined access to the mount and will freely share data from the mount and both will be able to control it - incredibly handy too!ĭoing this will confirm at all times that the mount is working using ASCOM/EQMod so you will be able to fault-find Starry Night more easily.Sorry about the delay, lots of research and thinking to be done about this one. Now see if MaximDL will control the mount.Īssuming that all is well with MaximDL, turn to Starry Night and configure it using the ASCOM option to also point to 'POTH'. Now configure POTH to use the EQMod driver (Options - Setup - Choose 'Scope). Next, go to Maxim DL and select the telescope control panel and choose 'POTH' as your telescope. This also works with the EQMod Simulator if that doesn't appear in the ASCOM chooser drop down. ![]() Go to the directory that stores the EQMod downloads and double click on EQMOD.EXE This will come up with an error message stating that it is an ASCOM driver and cannot be run 'standalone' ! This is quite rue but for some reason this procedure registers the EQMod driver with ASCOM beautifully. From what I can see, you are using EQMod so there is NO need for you to have the Celestron drivers in place at all as you will be connecting to the 'scope via ASCOM and the ASCOM EQMod driver. I am a little confused by one aspect of this.
0 Comments
Leave a Reply. |
AuthorWrite something about yourself. No need to be fancy, just an overview. ArchivesCategories |