VOGONS


Logitech Scanman Color on Windows 9x?

Topic actions

First post, by kikendo

User metadata
Rank Member
Rank
Member

I got a Logitech Scanman Color with its own ISA card interface, and I am unable to get it work with the included software that I got with it, which is clearly made for Windows 3.x
Does anyone know if this beast has drivers made specifically for Windows 9x? Or has any idea how to get this working with Windows 9x?

Reply 1 of 20, by Horun

User metadata
Rank l33t++
Rank
l33t++

From their archives sounds like you need Logitech ScanWare 2.2 driver disks. Found them and other good info in their FAQ file list:
http://web.archive.org/web/19990508141444/htt … ort/hhscan.html
http://web.archive.org/web/19991006223111/htt … pport/2620.html
yes they will properly download 😀

added: this FAQ goes over the adapter cards jumpers or switch settings.
http://web.archive.org/web/19991007033004/htt … pport/2651.html
created a .PDF of that page and attached

Hate posting a reply and then have to edit it because it made no sense 😁 First computer was an IBM 3270 workstation with CGA monitor. Stuff: https://archive.org/details/@horun

Reply 2 of 20, by darry

User metadata
Rank l33t++
Rank
l33t++
kikendo wrote on 2025-05-13, 23:04:

I got a Logitech Scanman Color with its own ISA card interface, and I am unable to get it work with the included software that I got with it, which is clearly made for Windows 3.x
Does anyone know if this beast has drivers made specifically for Windows 9x? Or has any idea how to get this working with Windows 9x?

I seem to recall that those scanners will not work at all if one has 16MB or more of RAM.

I believe the online documentation/help referenced this.

Not 100% sure of that.

EDIT: I see one of links @Horun shared mentions a patch for that.

Reply 3 of 20, by kikendo

User metadata
Rank Member
Rank
Member

This is all excellent info. Thank you!
I just wrecked my Windows 98 install after installing the fucking 16 bit drivers 🤣 so after I manage to install Windows again (it's giving me an unusually hard time on this machine!) I will try these solutions and report back.
This morning I was thinking that I should have checked the Wayback machine, I always forget it exists and that you can find a lot of this stuff there!

Reply 4 of 20, by PC Hoarder Patrol

User metadata
Rank l33t
Rank
l33t
kikendo wrote on 2025-05-14, 13:16:

This is all excellent info. Thank you!
I just wrecked my Windows 98 install after installing the fucking 16 bit drivers 🤣 so after I manage to install Windows again (it's giving me an unusually hard time on this machine!) I will try these solutions and report back.
This morning I was thinking that I should have checked the Wayback machine, I always forget it exists and that you can find a lot of this stuff there!

This one perhaps...dug it out the other week on the back of another post, though I'll wait until I find my original ScanWare 2.2 disks until I try it out ( assuming any of it still works after probably 20+ years! )

The attachment ScanMan Color 01.jpg is no longer available
The attachment ScanMan Color 02.jpg is no longer available

Reply 5 of 20, by kikendo

User metadata
Rank Member
Rank
Member

Thanks to Horun's help, I managed to get this working without ruining my (new) Windows 98 installation!
However I think the scanner is broken, the images look all green and weird.

NslGEjJ.jpeg

Seems like I have been sold a dud, maybe I can get another one, but this time, I'd get a parallel port one, because faffing about with the ISA card was a right pain in the ass (and I rather have a soundcard there!).
I can still use it for weird grayscale scans, I got this to fuck around so not all is completely lost, but I'll probably just try to get another one.
This one just looks soooo cool, I am a big Logitech collector from everything from this period.

Reply 6 of 20, by Jo22

User metadata
Rank l33t++
Rank
l33t++

Tip: As a workaround, try Windows 3.1x. :) And use 16 or 256c display driver.
Windows for Workgroups has Super VGA drivers and they work as intended, although them being unaccelerated.

"Time, it seems, doesn't flow. For some it's fast, for some it's slow.
In what to one race is no time at all, another race can rise and fall..." - The Minstrel

//My video channel//

Reply 7 of 20, by kikendo

User metadata
Rank Member
Rank
Member
Jo22 wrote on 2025-05-14, 19:36:

Tip: As a workaround, try Windows 3.1x. 😀 And use 16 or 256c display driver.
Windows for Workgroups has Super VGA drivers and they work as intended, although them being unaccelerated.

What does that have to do with the scanner acquiring images wrongly?

Reply 8 of 20, by Jo22

User metadata
Rank l33t++
Rank
l33t++
kikendo wrote on 2025-05-14, 21:25:
Jo22 wrote on 2025-05-14, 19:36:

Tip: As a workaround, try Windows 3.1x. 😀 And use 16 or 256c display driver.
Windows for Workgroups has Super VGA drivers and they work as intended, although them being unaccelerated.

What does that have to do with the scanner acquiring images wrongly?

Hi, it's because of GDI and graphics rendering.
Windows 3.x GDI was different to that used in Windows 9x.
Windows 3.x graphics drivers had contained a big junk of GDI code.
In Windows 9x, GDI was in the system files and only the hardware abstraction was in the graphics drivers (mini drivers).

Edit: Windows 98SE does render the WinG spinning cube demo incorrectly, depending on the graphics drivers.
Dithering and support for 256 colours doesn't work correctly.
Something similar could be the issue with the ScanMan software.
Re: Uses for Each Windows

"Time, it seems, doesn't flow. For some it's fast, for some it's slow.
In what to one race is no time at all, another race can rise and fall..." - The Minstrel

//My video channel//

Reply 9 of 20, by darry

User metadata
Rank l33t++
Rank
l33t++
Jo22 wrote on 2025-05-15, 05:58:
Hi, it's because of GDI and graphics rendering. Windows 3.x GDI was different to that used in Windows 9x. Windows 3.x graphics d […]
Show full quote
kikendo wrote on 2025-05-14, 21:25:
Jo22 wrote on 2025-05-14, 19:36:

Tip: As a workaround, try Windows 3.1x. 😀 And use 16 or 256c display driver.
Windows for Workgroups has Super VGA drivers and they work as intended, although them being unaccelerated.

What does that have to do with the scanner acquiring images wrongly?

Hi, it's because of GDI and graphics rendering.
Windows 3.x GDI was different to that used in Windows 9x.
Windows 3.x graphics drivers had contained a big junk of GDI code.
In Windows 9x, GDI was in the system files and only the hardware abstraction was in the graphics drivers (mini drivers).

Edit: Windows 98SE does render the WinG spinning cube demo incorrectly, depending on the graphics drivers.
Dithering and support for 256 colours doesn't work correctly.
Something similar could be the issue with the ScanMan software.
Re: Uses for Each Windows

Just to clarify what I believe you are trying to imply, while not explicitly stating ( please correct me if I am wrong), the Logitech software image processing pipeline for on screen display may be sharing code paths, using/setting some of the same variables, etc as what is used to either actually generate bitmaps from the raw scanned image data or at least or to preview it on screen.

In such a scenario, a bug that causes display corruption at certain color depths might also affect the actual scanned images or at least their on screen preview.

I hope that this is what you meant.

Reply 10 of 20, by Jo22

User metadata
Rank l33t++
Rank
l33t++
darry wrote on 2025-05-15, 11:27:

Just to clarify what I believe you are trying to imply, while not explicitly stating ( please correct me if I am wrong), the Logitech software image processing pipeline for on screen display may be sharing code paths, using/setting some of the same variables, etc as what is used to either actually generate bitmaps from the raw scanned image data or at least or to preview it on screen.

In such a scenario, a bug that causes display corruption at certain color depths might also affect the actual scanned images or at least their on screen preview.

I hope that this is what you meant.

Hi, yes, that's right. ^^ GDI was used for all sorts of things, I think..
There were GDI printers (Windows printer), for example.
It could be that GDI also was being used by the scanner software.
Maybe it's using something like WinDIB, not sure.

In case of doubt, it might be good to check out the scanner on Windows 3.1x or DOS.
Older handy scanner models shipped with both DOS and Windows software.
If there's a DOS software available for this model,
it maybe can used on that Windows 98PC without being required to install Windows 3.1x.

Anyway, just saying. It would be sad to throw that handy scanner away if the hardware merely seems broken but isn't, really.
I mean, the scanner apparently still works, the objects/forms are perfect.
Merely the wrong colours are weird..

"Time, it seems, doesn't flow. For some it's fast, for some it's slow.
In what to one race is no time at all, another race can rise and fall..." - The Minstrel

//My video channel//

Reply 11 of 20, by kikendo

User metadata
Rank Member
Rank
Member

OK, but supposedly, Windows 9x is supported, so why would Logitech release drivers that don't work correctly on Windows 9x?
I don't have a Windows 3.11 setup to test now, but if I wanted to use Windows 3.11, I wouldn't be here.
I downloaded a DOS driver from the links posted above but I have no software to test it with. Any ideas?

I'm not throwing anything away anyway, but I would like to use it 🙁

Reply 12 of 20, by Horun

User metadata
Rank l33t++
Rank
l33t++

There were some DOS scanner apps, one was Scan Edit II (Re: Looking for Image Scanning software DOS (8086) or Windows 3.0 (8086, Real mode)) am sure there were others...

Hate posting a reply and then have to edit it because it made no sense 😁 First computer was an IBM 3270 workstation with CGA monitor. Stuff: https://archive.org/details/@horun

Reply 13 of 20, by darry

User metadata
Rank l33t++
Rank
l33t++
kikendo wrote on 2025-05-16, 00:15:
OK, but supposedly, Windows 9x is supported, so why would Logitech release drivers that don't work correctly on Windows 9x? I do […]
Show full quote

OK, but supposedly, Windows 9x is supported, so why would Logitech release drivers that don't work correctly on Windows 9x?
I don't have a Windows 3.11 setup to test now, but if I wanted to use Windows 3.11, I wouldn't be here.
I downloaded a DOS driver from the links posted above but I have no software to test it with. Any ideas?

I'm not throwing anything away anyway, but I would like to use it 🙁

I am pretty sure the grayscale parallel Logitech scanner I had still managed to work in Windows 95 at least, before I replaced it. I remember the thing was quirky even on the best of days even in Windows 3.1 . I don't recall whether I had more issues in Windows 95 than 3.1, but I can definitely say that I was extremely happy to get a full page scanner sometime in the later half of the 1990s.

Still worth trying in 256-color display, as a test, IMHO and possibly in a temporary test install of Windows 3.1, just to test in the software environment that this thing was likely initially designed to run in. If it does not run any better in Windows 3.1, you can at least eliminate that as a variable.

When Windows 95 came out, plenty of manufacturers rushed out drivers or patches to support it. Not all of them were all that good. Add to that 30 years of aging to the hardware (risk of degradation or failure), potential incompatibilities due hardware generation gap (including but not limited to speed sensitivity) and loss of what was potentially known in terms of workarounds and quirks and you've plenty of variables and (un)known (un)knowns.

Reply 14 of 20, by kikendo

User metadata
Rank Member
Rank
Member

This is all great info, who would have thought it could be so problematic.
I am not entirely sure, though, that my Pentium III machine will be able to run Windows 3.11 though. My other option is a PII, so I am shit out of luck. I have long gotten rid of my 386 machines.
Need to see how to figure this out.

Reply 15 of 20, by Jo22

User metadata
Rank l33t++
Rank
l33t++
kikendo wrote on 2025-05-16, 13:11:

This is all great info, who would have thought it could be so problematic.
I am not entirely sure, though, that my Pentium III machine will be able to run Windows 3.11 though. My other option is a PII, so I am shit out of luck. I have long gotten rid of my 386 machines.
Need to see how to figure this out.

I'm surprised, as well. I once had a similar handy scanner by Mustek.
It had shipped Windows 3.1 drivers that still worked on 98SE and XP (!)
That's very interesting, because Windows XP runs everything 16-Bit in NTVDM/WoW.
Only explanation that comes to mind is that TWAIN drivers are no real "drivers" but more like a DLL.

"Time, it seems, doesn't flow. For some it's fast, for some it's slow.
In what to one race is no time at all, another race can rise and fall..." - The Minstrel

//My video channel//

Reply 16 of 20, by kikendo

User metadata
Rank Member
Rank
Member
Jo22 wrote on 2025-05-16, 13:26:
I'm surprised, as well. I once had a similar handy scanner by Mustek. It had shipped Windows 3.1 drivers that still worked on 98 […]
Show full quote

I'm surprised, as well. I once had a similar handy scanner by Mustek.
It had shipped Windows 3.1 drivers that still worked on 98SE and XP (!)
That's very interesting, because Windows XP runs everything 16-Bit in NTVDM/WoW.
Only explanation that comes to mind is that TWAIN drivers are no real "drivers" but more like a DLL.

I don't know technical details,. but the drivers are VXD files.
I've seen those Mustek scanners around, maybe I should have grabbed one of those. I got these because Logitech is a good brand and I love the design but this is turning out to be a stinker.

Thins I tried just now:
- running Windows 98 in 256 color, 640x480 mode. Same reuslts.
- trying to install the DOS drivers to try Scan Edit as suggested before. The drivers installation says my board isn't installed, even though it is.

I guess it just won't work on this newer computer 🙁

Reply 17 of 20, by Jo22

User metadata
Rank l33t++
Rank
l33t++
kikendo wrote on 2025-05-16, 13:30:
Jo22 wrote on 2025-05-16, 13:26:
I'm surprised, as well. I once had a similar handy scanner by Mustek. It had shipped Windows 3.1 drivers that still worked on 98 […]
Show full quote

I'm surprised, as well. I once had a similar handy scanner by Mustek.
It had shipped Windows 3.1 drivers that still worked on 98SE and XP (!)
That's very interesting, because Windows XP runs everything 16-Bit in NTVDM/WoW.
Only explanation that comes to mind is that TWAIN drivers are no real "drivers" but more like a DLL.

I don't know technical details,. but the drivers are VXD files.

Hi, ther drivers I had were both VXD and DRV (or just DRV).
That's because I was a 286 user running Windows 3.10.
So the driver must have been existed in 16-Bit version, too, because the 286 can't load VXDs.

I've seen those Mustek scanners around, maybe I should have grabbed one of those.

Maybe, yes. My model was a dark gray model that I can't find online anymore.
It had a light gray button on top, to start scanning process.
The interface card was a very slim 16-Bit ISA card with a round socket on the bracket side.

Maybe I can find a copy of the old driver disk, eventually.
(I didn't throw the a scanner away back then, but gave it to an elderly computer fan.)

I got these because Logitech is a good brand and I love the design but this is turning out to be a stinker.

Hey, it IS an iconic piece of history! You didn't do anything wrong here as far as I can tell! 🙂

Maybe you'll get your hands on a Compaq portable one day?
Some 386 and 486 models had flat screen and ISA slots (option).
Just comes to mind, because they don't take up much space. You can store them under bed, literally.

"Time, it seems, doesn't flow. For some it's fast, for some it's slow.
In what to one race is no time at all, another race can rise and fall..." - The Minstrel

//My video channel//

Reply 18 of 20, by PC Hoarder Patrol

User metadata
Rank l33t
Rank
l33t
kikendo wrote on 2025-05-16, 13:11:

This is all great info, who would have thought it could be so problematic.
I am not entirely sure, though, that my Pentium III machine will be able to run Windows 3.11 though. My other option is a PII, so I am shit out of luck. I have long gotten rid of my 386 machines.
Need to see how to figure this out.

Pretty sure this woks fine on some flavour of Win 9x...checked my archives and I can still see my scanner program group from Jan 96 (long since stopped using 3.x by then) with links to the FotoTouch Color (ftcolor.exe) and FTGRAY (touch.exe) apps.

I'll be checking mine in the next day or two, so will throw it on a 9x test rig and report back.

Reply 19 of 20, by kikendo

User metadata
Rank Member
Rank
Member
PC Hoarder Patrol wrote on 2025-05-17, 05:30:

Pretty sure this woks fine on some flavour of Win 9x...checked my archives and I can still see my scanner program group from Jan 96 (long since stopped using 3.x by then) with links to the FotoTouch Color (ftcolor.exe) and FTGRAY (touch.exe) apps.

I'll be checking mine in the next day or two, so will throw it on a 9x test rig and report back.

Thanks! Looking forward to your tests. What scanner do you have?