Windows 10 and Laser printer

[Rene Lamontagne]

Windows 10 version 1903 OS build 18362.239.
Printer Okidata c5150n, driver C51200GDEA.exe
Couple days ago I sent a file to the printer but nothing happened, I
last used it a couple weeks ago and it was fine then.
Did a bunch of things such as delete and reinstall driver, tried it in
USB and network modes, nothing, no messages or warnings but found it had
disappeared from the add printers page, tried to add printer but no
luck, tried new Lan and USB cables, zilch, Ran up a Linux Mint live USB
stick and the printer works fine, Same for MX Linux.
So the printer is OK and it has to be our friendly Windows again with
their lovely update gifts , I suspect another crappy update so even
tried a new fresh install, Nope still no printer, So who has an idea on
how to proceed now?
thanks for all help and ideas.

Rene

[Andreas Kohlbach]

Other than setting up a Linux print server with CUPS and let Windows use
it as relay, none. Well, go back some Windows updates. I seem to remember
that you can run older versions of packages.
--
Andreas

My random thoughts and comments
https://news-commentaries.blogspot.com/

[Johnny]

On Thu, 22 Aug 2019 13:15:14 -0500

Maybe Windows 10 just stopped supporting it. I think I remember you
saying it was an old printer.

I just wanted to tell you, that now you can make the scroll bars as
wide as you want them in Linux Mint Cinnamon.

[Rene Lamontagne]

Bought in June, 2007, makes it 12 years old. But was printing perfectly,
only a half dozen minor paper jams during that period. Gotta look at
Andreas suggestion re older updates.

Rene

[Rene Lamontagne]

On 2019-08-22 2:39 p.m., Andreas Kohlbach wrote:

> On Thu, 22 Aug 2019 14:00:03 -0500, Johnny wrote:
>>
>> On Thu, 22 Aug 2019 13:15:14 -0500
>> Rene Lamontagne <rla...@shaw.ca> wrote:
>>
>>> Windows 10 version 1903 OS build 18362.239.
>>> Printer Okidata c5150n, driver C51200GDEA.exe
>>> Couple days ago I sent a file to the printer but nothing happened, I
>>> last used it a couple weeks ago and it was fine then.
>>> Did a bunch of things such as delete and reinstall driver, tried it
>>> in USB and network modes, nothing, no messages or warnings but found
>>> it had disappeared from the add printers page, tried to add printer
>>> but no luck, tried new Lan and USB cables, zilch, Ran up a Linux Mint
>>> live USB stick and the printer works fine, Same for MX Linux.
>>> So the printer is OK and it has to be our friendly Windows again with
>>> their lovely update gifts , I suspect another crappy update so even
>>> tried a new fresh install, Nope still no printer, So who has an idea
>>> on how to proceed now?
>>> thanks for all help and ideas.
>>

>> Maybe Windows 10 just stopped supporting it. I think I remember you
>> saying it was an old printer.
>

> Then he should find an exclamation mark in the list of drivers for his
> printer.
>


there is no listing for my printer in Windows, The driver I have been
using is the original OKI driver since about 2009.

Rene

[Bob Eager]

Have you asked it to go online and check? I have a 1993 printer where I
have to do that.

[Rene Lamontagne]

On 2019-08-22 3:16 p.m., Andreas Kohlbach wrote:
> On Thu, 22 Aug 2019 14:52:59 -0500, Rene Lamontagne wrote:
>>

>> On 2019-08-22 2:39 p.m., Andreas Kohlbach wrote:
>>> On Thu, 22 Aug 2019 14:00:03 -0500, Johnny wrote:
>>>>
>>>> On Thu, 22 Aug 2019 13:15:14 -0500
>>

>>>> Maybe Windows 10 just stopped supporting it. I think I remember you
>>>> saying it was an old printer.
>>>
>>> Then he should find an exclamation mark in the list of drivers for his
>>> printer.
>>
>> there is no listing for my printer in Windows, The driver I have been
>> using is the original OKI driver since about 2009.
>

> Was Windows 10 installed back in 2009? I understand that you mitigated
> from an earlier Windows version to Windows 10 and the printer worked fine
> for some time. But recently suddenly refused to work. Then there should
> be an exclamation mark when you list your drivers.
>
> Since you mentioned it works with Linux and you have a spare PC, install
> Linux on it to be a print server Windows clients can use.
>

Got it worked out, after trying everything I could think of (Except
standing on my head and yodeling). :-)
I started looking through all the files in the folder where I had
installed the Oki C51200GDEA.exe driver and finally found an inf file,
on a hunch I right clicked on it and there was an *install* option, So I
clicked it and then went back to devices and printers page and there it
was,Thank all the Deities that I got it working again.
The path was Okidata> c5150_5200 >English >gdi >32 or 64 bit
>Ok7242he.inf >right click install.
That was a great feeling as that printer was $700.00 when I bought it
and its been trouble free for all those years.
I don"t know exactly what caused the problem or why that fixed it, But
i do know from years back that an inf file with an install option is
always worth a try.

Thanks to all who tried to help.

Rene

[Eric Stevens]

On Thu, 22 Aug 2019 14:52:59 -0500, Rene Lamontagne <rla...@shaw.ca>
wrote:

I have an OKI C5600 of about that age or possibly slightly older. Its
running quite happily on Windows 10 via a network. I had a driver and
installation software and it loaded and installed quite easily.

Have you looked at
https://okiprinting-en-gb.custhelp.com/app/answers/detail/a_id/2997/~/oki-printer-drivers-compatibility-with-windows-10
or similar?
>
>Rene

--


Eric Stevens

There are two classes of people. Those who divide people into
two classes and those who don't. I belong to the second class.

[Rene Lamontagne]

It's good to go now Eric, the driver was and always worked good good in
Windows 10 but something screwed with it somehow and made it jump the rails.

Rene

[Rabid Robot]

Score one for Linux in its dedication to supporting all hardware whether
outdated or not.

[Eric Stevens]

On Thu, 22 Aug 2019 18:22:48 -0500, Rene Lamontagne <rla...@shaw.ca>
wrote:

I don't know when I got into the the habit but over the years I have
saved an 'Inwards' folder which itself contains folders:

Acronis
Adobe
Agent 8
Agent Ransack
Apple
Arcam
Belarc Advisor
etc. ...

... which in contain copies of all the files (and more folders) of the
software which installed the software on which I depend. For example I
have one:

Oki > C5600 > C5600_C5600Win7x64_ENU226_tcm3-364...

... which installs the driver for the OKI C5600. I don't know how I
would do a complete reinstall of Windows without all this.

[Paul]

With Windows, keeping a printer running is a measure of
your ingenuity. It's possible to make ancient crap run,
if you know all the recipes. Sometimes, a "look alike"
driver happens to make another printer run. There
are "universal drivers" for some printer categories
(more than one category too), which can be used if
the manufacturer doesn't have a specific driver.
I was using that approach, to build a "Postscript printer
to FILE" for some of my setups here. (I was then
using Distiller to make PDFs from that. Windows 10
makes PDFs directly, so that approach isn't necessary
there now.)

What Rene just did, try an INF, is just one of the
options. There is also some Windows Update thing,
where a whole library of ancient printer drivers
(maybe even some dot matrix ones) get downloaded,
and "that takes an hour to download". So whatever
that recipe involves, the arrival of the "kit" is
rather lengthy, and might well be fetched one
package at a time, rather than being a giant
ZIP or something.

The trick then, for the poor end user owning just one
printer, is which one of those methods will offer
"good fishing". And odds are, there isn't a single
web page "documenting all the fishing holes you can try".

It was the same way with scanners. Some people here, would
offer advice right away to just "give up". But some
posters manage to get their scanner running anyway,
through dogged persistence.

Paul

[Eric Stevens]

On Fri, 23 Aug 2019 01:27:01 -0400, Paul <nos...@needed.invalid>
wrote:

At the other end of the life cycle the advice should be to buy a good
and uptodate printer liable to be supported for a long time. I tend to
do that when buying gear and this thread has brought me to the
realisation that I am still able to run my 15 year old printer under
Windows 10.

[Rene Lamontagne]

Yes, I did try the Windows update thing and It took forever but alas, my
printer was not listed, The thing was I have the proper OKI driver and
it installs fine but something in Windows was breaking it, Running that
inf cured it for whatever reason.
Okidata makes great printers and good drivers, 12 years and the original
driver still works in Windows 10.

Rene

[Paul]

It's possible, during an OS Upgrade (to 1903), that the INF did
not get re-applied to the OS. The drivers may be getting
reinstalled, after Windows is moved to Windows.old . A new
Windows folder is built. Something has to put drivers in it.
Maybe only certain driver installation formats are supported.
(The OS likes to cache .msi files perhaps.) I don't know
if "bare" INF files receive as good coverage. They should,
realistically speaking. There should be a feature for that,
because it's a basic way that Device Manager has of installing
a driver. Is the signing "right" for that, on an older
driver ? Who knows. They've switched to SHA2 only very
recently for Windows Update, but that isn't likely to
apply to drivers - with drivers it's more likely to be
"signing" with some sort of certificate, as proof of purchase.

I think that was a problem for SpeedFan at one time. You
couldn't install giveio.sys in an x64 system, unless
the driver was "signed". The author of SpeedFan then
had to set about getting a certificate for signing,
so this would still work. Giveio was some means
of "punching thru" the Ring 3 to Ring 0 area,
so the fan speed registers could be written.
Companies like Asus got around this, by using an ACPI
driver (ATK0110), so they could have direct access
to hardware. And the BIOS would present an item as
an ACPI object in a BIOS table.

It's possible no changes are necessary to the driver
code, and merely "re-packaging" the driver installer
would fix it.

Some of the Promise storage cards, had dreadful drivers.
Because they required the INF method for everything.
And that's about the lowest form of support the OS
has. It takes a *lot* of practice, to become "good"
with Promise drivers. Like switching between RAID
and non-RAID drivers on a 378. Very hard to figure out
and do (hard to tell which driver is currently
installed and what to do next). And with no documentation
of note, you had to figure this stuff out on your own.

With packaged drivers, the OS seems to do a better job.

Paul

[Ammammata]

Il giorno Thu 22 Aug 2019 08:15:14p, *Rene Lamontagne* ha inviato su
alt.comp.os.windows-10 il messaggio news:gs84dk...@mid.individual.net.
Vediamo cosa ha scritto:

> So the printer is OK and it has to be our friendly Windows again with
> their lovely update gifts , I suspect another crappy update so even
> tried a new fresh install, Nope still no printer, So who has an idea on
> how to proceed now?
> thanks for all help and ideas.
>

system restore

--
/-\ /\/\ /\/\ /-\ /\/\ /\/\ /-\ T /-\
-=- -=- -=- -=- -=- -=- -=- -=- - -=-
>>>>> http://www.bb2002.it :) <<<<<
........... [ al lavoro ] ...........

[Frank Slootweg]

Eric Stevens <eric.s...@sum.co.nz> wrote:
[...]

> I don't know when I got into the the habit but over the years I have
> saved an 'Inwards' folder which itself contains folders:
>
> Acronis
> Adobe
> Agent 8
> Agent Ransack
> Apple
> Arcam
> Belarc Advisor
> etc. ...
>
> ... which in contain copies of all the files (and more folders) of the
> software which installed the software on which I depend. For example I
> have one:
>
> Oki > C5600 > C5600_C5600Win7x64_ENU226_tcm3-364...
>
> ... which installs the driver for the OKI C5600. I don't know how I
> would do a complete reinstall of Windows without all this.

Indeed. I follow a similar procedure. To be [f|F]rank, I didn't know
there was any other way to do it! :-)

For any additional - i.e. not part of Windows - software, I keep the
installation package - in my case in C:\packages - *and* document how I
installed that software on my system. So if something stops working, or
I move to another computer/Windows-version, etc., I just have to check
my notes. I.e. in a case comparable to the OP, my documentation file
HP_LaserJet_Pro_M1132_MFP.

Elementary, dear Watson!

[Andreas Kohlbach]

On Fri, 23 Aug 2019 01:27:01 -0400, Paul wrote:

>
> Rabid Robot wrote:
>>
>> Score one for Linux in its dedication to supporting all hardware whether
>> outdated or not.
>>
>
> With Windows, keeping a printer running is a measure of
> your ingenuity.

With any printer not working with Windows (Mac, what ever) but Linux, as
I mentioned in another article, set Linux up as a print server. For
Windows a network printer appears it sends the job to. Linux does the rest.
--
Andreas

[Jeff-Relf.Me]

Rene_Lamontagne,

Un-install your Okidata c5150n Printer completely.

Reinstall it using a version that works with Windows 10 x64.

[Rene Lamontagne]

It's fixed read previous posts.

Rene

[Jackie Webster]

I know this is an ancient post, but I am trying to locate a copy of the Ok7242he.inf file. I am trying to run my OKI C5200 on Windows 10. I've tried a variety of generic drivers, but nothing is working. I was hoping perhaps your solution would work for me. I can't locate my original installation disks. Thanks so much if you might be able to assist!

[Bobby Berg]

Rene,
Thank you for that post about the .inf file in the Oki installation folder! My old computer, running Windows 10, printed to my Oki C5150 just fine, so I found the installation executable in the old Downloads folder, copied it to the new computer, and ran it. Windows still didn't see the printer, but right-clicking on the "Ok7242he.inf" file and clicking Install got it there.
Bobby