I now own an 8000Hiresolve Howtek. Just bought it. Should be here in about 4 weeks or so.
I now own an 8000Hiresolve Howtek. Just bought it. Should be here in about 4 weeks or so.
Does anybody have the 4500 FST software for windows? I didn't get a chance to download it before everything was deleted off the Scan-Hi-End group.
Thanks!
Ethan | Flickr | www.vancouverdrumscan.com
There is no FST for windows, DOS only.
Ethan | Flickr | www.vancouverdrumscan.com
I posted what I have a few posts back. I'm not aware of any other version of field service test for 4000/4500...
Not sure how I missed that. Thank you!
Ethan | Flickr | www.vancouverdrumscan.com
Hi All,
I'm trying to get our Howtek scanmaster 7500 up and running at work. We are running DPL 8.1 in Windows 10 using bootcamp, on a 2013 iMac, with a Ratoc SCSI>USB adapter. Our current problem is that DPL does not see the scanner, in Device Manager we get an error with the USB device. All the drivers have been installed correctly, we're working with evan at Aztek and sending in our adapters to him to inspect. However, I wanted to see if any of you on here who are running a similar set-up could share any advice, since I know that Bootcamp Windows can be a bit quirky and maybe there is some strange thing I need to change in the drivers or the Registry Editor or something. Has anyone had a similar issue? It has been so much work to get this scanner here and we are so close yet so far!
Hi, We are trying to run a very similar setup to yours, did you ever have issues getting your Windows 10 shell to recognize your USB adapter?
FYI, you can put together a PC and use a number of SCSI cards that are proven to play nicely with Howtek scanners. All that for half the cost of a Ratoc SCSI-USB adapter alone.
Hi csbrk9. I got an Aztek Premiere running with DPL 8 on a 2013 Mac Pro with Windows 10 running in Parallels using the Ratoc SCSI to USB adapter that way I could just flick back and forth between the Mac OS and Windows without needing to reboot. I vaguely remember trying it in Bootcamp, but found Parallels better since it has a nice interface for determining which USB devices I wanted connected to the Windows OS and which ones I wanted to keep with my Mac OS, which might have helped me avoid device conflicts. Parallels basically pulled the mouse and keyboard over virtually, so the Ratoc adapter and sometimes an external drive were the only devices attached to the Windows OS.
I usually ran into problems if I didn't have the drum scanner fully booted up before I started Windows. If for some reason the drum scanner didn't appear in the drop down menu within DPL I could close DPL and open Device Manager, right-click on the name of my computer in device manager, and select Scan For Hardware Changes and the scanner would show. Then when I reopened DPL the scanner would be listed there as well. I was also running the Ratoc adapter without the included extension cable attached; I don't know if that made a difference. I never had to change anything with the registry or do anything fancy when I installed the drivers. The hardest part was figuring out the best way to install Windows. I also had nothing else installed on Windows 10 when I set up the scanner, so that probably also helped avoid device conflicts.
Those are the things that worked for me. But it sounds like you're getting a yellow triangle error next to the device in device manager. The build you're trying for is definitely possible, but it there's clearly a conflict somewhere. You've probably tried most of these things, but to troubleshoot you can try (1) try plugging it into a different port, it could be a problem with the bus the port is on and an allocation of shared resources there, (2) unplugging all other devices from the Mac and do a fresh install of Windows. Hopefully without any other devices attached there wouldn't be a conflict in resources, which is what the yellow triangle often means, (3) trying going through the same steps to set it up, but on a different Mac to see if the issue is the particular internals of the Mac you started with, (4) try installing Windows 10 through Parallels instead of Bootcamp to see if that gives you more control over what devices Windows 10 is seeing to cut down on sources of conflict.
I hope that helps!
Bookmarks