Unsigned drivers

[A-Mac]

An unsigned driver that came with Nero CD-Rom software caused my pc system,
registry and disk to cobble up. Windows did its best to keep going.
If your DVD/CD [or any plug-ins, etc.] came with the pc, there will probably
be unsigned drivers in the s/w. It is unfair that the buyer should have to
purchase signed drivers and/or repair s/w. This problem should be addressed
at source, as it is as bad as a virus attack.

 

[David H. Lipman]

From: "A-Mac" <[email protected].(donotspam)>

| An unsigned driver that came with Nero CD-Rom software caused my pc system,
| registry and disk to cobble up. Windows did its best to keep going.
| If your DVD/CD [or any plug-ins, etc.] came with the pc, there will probably
| be unsigned drivers in the s/w. It is unfair that the buyer should have to
| purchase signed drivers and/or repair s/w. This problem should be addressed
| at source, as it is as bad as a virus attack.
| --
| Old_and_forgotten

Too phunny !

 

[JS]

What version of Nero was it?

 

[Jose]

An unsigned driver that came with Nero CD-Rom software caused my pc system,
registry and disk to cobble up.  Windows did its best to keep going.
If your DVD/CD [or any plug-ins, etc.] came with the pc, there will probably
be unsigned drivers in the s/w.  It is unfair that the buyer should have to
purchase signed drivers and/or repair s/w.  This problem should be addressed
at source, as it is as bad as a virus attack.

If Windows encounters a driver that is unsigned or the driver
signature differs from the a signed driver authority, you should be
given an option to install the driver or not. You can set up Windows
to not warn you at all. Proceeding is at your choice and your risk.

I think there must be plenty of functioning drivers in the world that
are unsigned. Maybe signing it is too much trouble, costs too much
to maintain, maybe they forgot about it, don't care or are just out of
sync after updates.

It is too bad you are having a problem, but you did not say what or
why you think it has anything to do with Nero or how your system and
registry got cobbled up and what you tried to do about it. Which
"unsigned driver" are you referencing? Did somebody try to sell you
one?

If you think you are having an issue that is related to a Nero driver,
what did they say when you described your problem to them through
their own support mechanism?

When you posted your situation to a Nero specific audience/news group/
forum what was the response?

Are you still having some problem?

Jose

 

[A-Mac]

To Jose
Nero repudiated it, said Windows could deal with it. Nero s/w (supplied
with pc)was to copy files back and forth C:/CD. Without the driver [from Oak
Technologies - can't recall its name] the Nero s/w wouldn't work. The
Windows Move, Copy is slower but surer. I also had some similar problems
with Roxio s/w that came with the external DVD rewrite (which have been
addressed with an update). My pc had a problem just after purchase: bad dimm
mem stick. This may have caused some internal sensitivity to h/w problems.
The Nero s/w [max date 2005] caused Startup Event error msg with Redbook;
"can't read digital audio input.."
My point was; my newer pc has some unsigned drivers for the DVD/CD, but
there are no problems, as it was a custom-built machine, not an off-the-shelf.
Apart from having to clean my disk and re-install everything, it is just
being nagged by MS about unsigned drivers and being forced into purchases [as
I said, previously] that is unfair.
Thanks for your interest.
--
Old_and_forgotten

An unsigned driver that came with Nero CD-Rom software caused my pc system,
registry and disk to cobble up. Windows did its best to keep going.
If your DVD/CD [or any plug-ins, etc.] came with the pc, there will probably
be unsigned drivers in the s/w. It is unfair that the buyer should have to
purchase signed drivers and/or repair s/w. This problem should be addressed
at source, as it is as bad as a virus attack.

If Windows encounters a driver that is unsigned or the driver
signature differs from the a signed driver authority, you should be
given an option to install the driver or not. You can set up Windows
to not warn you at all. Proceeding is at your choice and your risk.

I think there must be plenty of functioning drivers in the world that
are unsigned. Maybe signing it is too much trouble, costs too much
to maintain, maybe they forgot about it, don't care or are just out of
sync after updates.

It is too bad you are having a problem, but you did not say what or
why you think it has anything to do with Nero or how your system and
registry got cobbled up and what you tried to do about it. Which
"unsigned driver" are you referencing? Did somebody try to sell you
one?

If you think you are having an issue that is related to a Nero driver,
what did they say when you described your problem to them through
their own support mechanism?

When you posted your situation to a Nero specific audience/news group/
forum what was the response?

Are you still having some problem?

Jose

 

[David H. Lipman]

From: "A-Mac" <[email protected].(donotspam)>

| To Jose
| Nero repudiated it, said Windows could deal with it. Nero s/w (supplied
| with pc)was to copy files back and forth C:/CD. Without the driver [from Oak
| Technologies - can't recall its name] the Nero s/w wouldn't work. The
| Windows Move, Copy is slower but surer. I also had some similar problems
| with Roxio s/w that came with the external DVD rewrite (which have been
| addressed with an update). My pc had a problem just after purchase: bad dimm
| mem stick. This may have caused some internal sensitivity to h/w problems.
| The Nero s/w [max date 2005] caused Startup Event error msg with Redbook;
| "can't read digital audio input.."
| My point was; my newer pc has some unsigned drivers for the DVD/CD, but
| there are no problems, as it was a custom-built machine, not an off-the-shelf.
| Apart from having to clean my disk and re-install everything, it is just
| being nagged by MS about unsigned drivers and being forced into purchases [as
| I said, previously] that is unfair.
| Thanks for your interest.
| --
| Old_and_forgotten


"...being nagged by MS about unsigned drivers and being forced into purchases"

And gets even phunnier...

 

[Jose]

To Jose
Nero repudiated it, said Windows could deal with it.  Nero s/w (supplied
with pc)was to copy files back and forth C:/CD.  Without the driver [from Oak
Technologies - can't recall its name] the Nero s/w wouldn't work.  The
Windows Move, Copy is slower but surer.  I also had some similar problems
with Roxio s/w that came with the external DVD rewrite (which have been
addressed with an update).  My pc had a problem just after purchase: bad dimm
mem stick.  This may have caused some internal sensitivity to h/w problems.  
The Nero s/w [max date 2005] caused Startup Event error msg with Redbook;
"can't read digital audio input.."
My point was; my newer pc has some unsigned drivers for the DVD/CD, but
there are no problems, as it was a custom-built machine, not an off-the-shelf.
Apart from having to clean my disk and re-install everything, it is just
being nagged by MS about unsigned drivers and being forced into purchases[as
I said, previously] that is unfair.
Thanks for your interest.
--
Old_and_forgotten

An unsigned driver that came with Nero CD-Rom software caused my pc system,
registry and disk to cobble up.  Windows did its best to keep going..
If your DVD/CD [or any plug-ins, etc.] came with the pc, there will probably
be unsigned drivers in the s/w.  It is unfair that the buyer shouldhave to
purchase signed drivers and/or repair s/w.  This problem should be addressed
at source, as it is as bad as a virus attack.

If Windows encounters a driver that is unsigned or the driver
signature differs from the a signed driver authority, you should be
given an option to install the driver or not.  You can set up Windows
to not warn you at all.  Proceeding is at your choice and your risk.

I think there must be plenty of functioning drivers in the world that
are unsigned.  Maybe signing it is too much trouble,  costs too much
to maintain, maybe they forgot about it, don't care or are just out of
sync after updates.

It is too bad you are having a problem, but you did not say what or
why you think it has anything to do with Nero or how your system and
registry got cobbled up and what you tried to do about it.  Which
"unsigned driver" are you referencing?  Did somebody try to sell you
one?

If you think you are having an issue that is related to a Nero driver,
what did they say when you described your problem to them through
their own support mechanism?

When you posted your situation to a Nero specific audience/news group/
forum what was the response?

Are you still having some problem?

Jose

I suppose it is within the rights of MS to blow you off for using
drivers that did are not signed. They are not in the business of
figuring out why some 3rd party software doesn't work - only their
software.

You situation is unfortunate but I think not a problem for Microsoft.

What happened when you looked on the Nero and Oak WWW sites to verify
you have the latest hardware and software drivers? I think updated
drivers are no charge items

They have their own online support and user forums with experts on
just these things. When you posted your error messages (whatever they
are) and situation out there, what did they recommend?

Are you sure you posted the exact error message verbatim (as close as
you can)? I searched a little and can't find anything close.

Jose

 

[Mike Hall - MVP]

An unsigned driver that came with Nero CD-Rom software caused my pc
system,
registry and disk to cobble up. Windows did its best to keep going.
If your DVD/CD [or any plug-ins, etc.] came with the pc, there will
probably
be unsigned drivers in the s/w. It is unfair that the buyer should have
to
purchase signed drivers and/or repair s/w. This problem should be
addressed
at source, as it is as bad as a virus attack.

Does this relate to Nero In-CD?

 

[Jose]

From: "A-Mac" <[email protected].(donotspam)>

| To Jose
| Nero repudiated it, said Windows could deal with it.  Nero s/w (supplied
| with pc)was to copy files back and forth C:/CD.  Without the driver [from Oak
| Technologies - can't recall its name] the Nero s/w wouldn't work.  The
| Windows Move, Copy is slower but surer.  I also had some similar problems
| with Roxio s/w that came with the external DVD rewrite (which have been
| addressed with an update).  My pc had a problem just after purchase: bad dimm
| mem stick.  This may have caused some internal sensitivity to h/w problems.
| The Nero s/w [max date 2005] caused Startup Event error msg with Redbook;
| "can't read digital audio input.."
| My point was; my newer pc has some unsigned drivers for the DVD/CD, but
| there are no problems, as it was a custom-built machine, not an off-the-shelf.
| Apart from having to clean my disk and re-install everything, it is just
| being nagged by MS about unsigned drivers and being forced into purchases [as
| I said, previously] that is unfair.
| Thanks for your interest.
| --
| Old_and_forgotten

"...being nagged by MS about unsigned drivers and being forced into purchases"

And gets even phunnier...  

I forgot to mention clearly my thoughts:

It is not Microsoft's job to make sure their software works with every
piece of hardware and driver in the world. It is the other way around.

 

[David H. Lipman]

From: "Jose" <[email protected]>

| I forgot to mention clearly my thoughts:

| It is not Microsoft's job to make sure their software works with every
| piece of hardware and driver in the world. It is the other way around.

He's also confused on the idea of a publisher's certificate in a signed driver. It
doesn't make or break a driver. Its a trust concept not a factor if it works or doesn't
work or if its free or paid for.

 

[A-Mac]

I guess it is just that things should improve. When one buys a piece of
equipment, the accompanying disc (if any) and its s/w are, notionally, free.
I still feel that these producers of unsigned s/w [I'm told that even the US
government uses bits of college student-produced s/w in some of its programs]
should tow the line as regards the companies who provide our operating
systems. Belkin, US Robotics and Hewlett Packard do this; Roxio is coming
around. We Users are the victims if we don't realise the problem. For all my
experience, I didn't. That is why I wanted to share my grief at a forum.

 

[Jose]

I guess it is just that things should improve.  When one buys a piece of
equipment, the accompanying disc (if any) and its s/w are, notionally, free.  
I still feel that these producers of unsigned s/w [I'm told that even theUS
government uses bits of college student-produced s/w in some of its programs]
should tow the line as regards the companies who provide our operating
systems. Belkin, US Robotics and Hewlett Packard do this; Roxio is coming
around. We Users are the victims if we don't realise the problem.  For all my
experience, I didn't.  That is why I wanted to share my grief at a forum.
--

From: "Jose" <[email protected]>

| I forgot to mention clearly my thoughts:

| It is not Microsoft's job to make sure their software works with every
| piece of hardware and driver in the world.  It is the other way around.

He's also confused on the idea of a publisher's certificate in a signeddriver.  It
doesn't make or break a driver.  Its a trust concept not a factor if it works or doesn't
work or if its free or paid for.

I don't think I have ever installed anything from a CD that comes with
some hardware. You can count on it being a one size fits all that
probably doesnt fit you and also out of date.

I have never installed anything from a CD just for a piece of hardware
- printer, scanner, camera, CD/DVD drive, mobile device, etc. Nope.
Never done it and never will. I have also never even heard of someone
having to purchase a driver to get something working.

It is too bad that you still have not specified what your problem is
(except you are grieved). You think some unsigned driver cobbled your
system and registry, but don't say why you think that. I would guess
you really have some other problem and somehow think it is because you
discoverd an unsigned driver. Unlikely.

Whatever your problem is, there is probably a solution for it, but
nobody knows what the problem is except you and you are not sharing.

We have asked several times for what hardware, what software, what
driver and you don't answer the questions. After 11 messages, I am
tired of guessing.

I feel some compassion for your grief (and that soon will pass), but
will not be able to help resolve a vague problem with no details.

Jose

 

[A-Mac]

Sorry for vagueness. Let me conclude:
The original problem is that the pc involved suffers when something goes
wrong [I did mention this].
Peripherally, I am, pro tem, stuck with it. It is working, now. But there
must be others out there who get h/w - s/w problems. My point is still about
drivers. When I traced the "nervous breakdown" back through all the errors,
the Registry file corruption, the memory and, finally, disk problem, via my
notes, it was definitely down to driver AFS2K.sys, from Oak Technologies.
The error msg was "This drive has not been shown to support digital audio
playback"; and MS feedback corroborrated a h/w problem with the CD drive (the
mechanics are fine).
I proved my pc's sensitivity when the [original, from the installer CD]
Belkin hub unsigned driver created telephony problems; such as causing the
system to disable some of the associated Services. Belkin d/ld a new, signed
driver, and no further problems occurred on that front. I hope this clarifies
things: You have been a faithful and helpful correspondent.
Old_and_forgotten

I guess it is just that things should improve. When one buys a piece of
equipment, the accompanying disc (if any) and its s/w are, notionally, free.
I still feel that these producers of unsigned s/w [I'm told that even the US
government uses bits of college student-produced s/w in some of its programs]
should tow the line as regards the companies who provide our operating
systems. Belkin, US Robotics and Hewlett Packard do this; Roxio is coming
around. We Users are the victims if we don't realise the problem. For all my
experience, I didn't. That is why I wanted to share my grief at a forum.
--

From: "Jose" <[email protected]>

| I forgot to mention clearly my thoughts:

| It is not Microsoft's job to make sure their software works with every
| piece of hardware and driver in the world. It is the other way around.

He's also confused on the idea of a publisher's certificate in a signed driver. It
doesn't make or break a driver. Its a trust concept not a factor if it works or doesn't
work or if its free or paid for.

I don't think I have ever installed anything from a CD that comes with
some hardware. You can count on it being a one size fits all that
probably doesnt fit you and also out of date.

I have never installed anything from a CD just for a piece of hardware
- printer, scanner, camera, CD/DVD drive, mobile device, etc. Nope.
Never done it and never will. I have also never even heard of someone
having to purchase a driver to get something working.

It is too bad that you still have not specified what your problem is
(except you are grieved). You think some unsigned driver cobbled your
system and registry, but don't say why you think that. I would guess
you really have some other problem and somehow think it is because you
discoverd an unsigned driver. Unlikely.

Whatever your problem is, there is probably a solution for it, but
nobody knows what the problem is except you and you are not sharing.

We have asked several times for what hardware, what software, what
driver and you don't answer the questions. After 11 messages, I am
tired of guessing.

I feel some compassion for your grief (and that soon will pass), but
will not be able to help resolve a vague problem with no details.

Jose

 

[A-Mac]

Things are changing. AFS2K.sys has turned up, SIGNED, after some Win XP
downloads. It caused some problems, at first, "The driver detected a
controller error \Device\CDRom1". But, after my tidying up the zapped Word
and Belkin s/w, it seems to be working. I don't think I'll try installing
Nero, again, though. Maybe that's why Nero Help told me the s/w was Windows'
responsibility.
Anyway, many thanks for all the advice.
--
Old_and_forgotten

An unsigned driver that came with Nero CD-Rom software caused my pc
system,
registry and disk to cobble up. Windows did its best to keep going.
If your DVD/CD [or any plug-ins, etc.] came with the pc, there will
probably
be unsigned drivers in the s/w. It is unfair that the buyer should have
to
purchase signed drivers and/or repair s/w. This problem should be
addressed
at source, as it is as bad as a virus attack.

Does this relate to Nero In-CD?

 

[Mike Hall - MVP]

Things are changing. AFS2K.sys has turned up, SIGNED, after some Win XP
downloads. It caused some problems, at first, "The driver detected a
controller error \Device\CDRom1". But, after my tidying up the zapped Word
and Belkin s/w, it seems to be working. I don't think I'll try installing
Nero, again, though. Maybe that's why Nero Help told me the s/w was
Windows'
responsibility.
Anyway, many thanks for all the advice.
--
Old_and_forgotten

An unsigned driver that came with Nero CD-Rom software caused my pc
system,
registry and disk to cobble up. Windows did its best to keep going.
If your DVD/CD [or any plug-ins, etc.] came with the pc, there will
probably
be unsigned drivers in the s/w. It is unfair that the buyer should
have
to
purchase signed drivers and/or repair s/w. This problem should be
addressed
at source, as it is as bad as a virus attack.

Does this relate to Nero In-CD?

When installing Nero, opt for the custom install and only install the
burning ROM part. The rest of it is just trouble..

 

[Jose]

Things are changing. AFS2K.sys has turned up, SIGNED, after some Win XP
downloads.  It caused some problems, at first, "The driver detected a
controller error \Device\CDRom1". But, after my tidying up the zapped Word
and Belkin s/w, it seems to be working.  I don't think I'll try installing
Nero, again, though.  Maybe that's why Nero Help told me the s/w was
Windows'
responsibility.
Anyway, many thanks for all the advice.

An unsigned driver that came with Nero CD-Rom software caused my pc
system,
registry and disk to cobble up.  Windows did its best to keep going.
If your DVD/CD [or any plug-ins, etc.] came with the pc, there will
probably
be unsigned drivers in the s/w.  It is unfair that the buyer should
have
to
purchase signed drivers and/or repair s/w.  This problem should be
addressed
at source, as it is as bad as a virus attack.

When installing Nero, opt for the custom install and only install the
burning ROM part. The rest of it is just trouble..

Yeah! Good advice.

Former Development Manager: "We'll not only sell 'em the gun, we'll
load it for 'em."

 

[A-Mac]

Yes. The "installation" disk Nero Express, with InCD, Acrobat Reader, etc.
--
Old_and_forgotten

Things are changing. AFS2K.sys has turned up, SIGNED, after some Win XP
downloads. It caused some problems, at first, "The driver detected a
controller error \Device\CDRom1". But, after my tidying up the zapped Word
and Belkin s/w, it seems to be working. I don't think I'll try installing
Nero, again, though. Maybe that's why Nero Help told me the s/w was
Windows'
responsibility.
Anyway, many thanks for all the advice.
--
Old_and_forgotten

An unsigned driver that came with Nero CD-Rom software caused my pc
system,
registry and disk to cobble up. Windows did its best to keep going.
If your DVD/CD [or any plug-ins, etc.] came with the pc, there will
probably
be unsigned drivers in the s/w. It is unfair that the buyer should
have
to
purchase signed drivers and/or repair s/w. This problem should be
addressed
at source, as it is as bad as a virus attack.
--
Old_and_forgotten


Does this relate to Nero In-CD?

When installing Nero, opt for the custom install and only install the
burning ROM part. The rest of it is just trouble..

 

[A-Mac]

Thanks. I think, now, there might be a h/w problem. Device Manager only
"sees" things when they are up and running.
--
Old_and_forgotten

Things are changing. AFS2K.sys has turned up, SIGNED, after some Win XP
downloads. It caused some problems, at first, "The driver detected a
controller error \Device\CDRom1". But, after my tidying up the zapped Word
and Belkin s/w, it seems to be working. I don't think I'll try installing
Nero, again, though. Maybe that's why Nero Help told me the s/w was
Windows'
responsibility.
Anyway, many thanks for all the advice.
--
Old_and_forgotten

An unsigned driver that came with Nero CD-Rom software caused my pc
system,
registry and disk to cobble up. Windows did its best to keep going.
If your DVD/CD [or any plug-ins, etc.] came with the pc, there will
probably
be unsigned drivers in the s/w. It is unfair that the buyer should
have
to
purchase signed drivers and/or repair s/w. This problem should be
addressed
at source, as it is as bad as a virus attack.
--
Old_and_forgotten


Does this relate to Nero In-CD?

When installing Nero, opt for the custom install and only install the
burning ROM part. The rest of it is just trouble..

 

[Al Falfa]

... Device Manager only "sees" things when they are up and running.

Control Panel > System > /Advanced\ [Environment Variables]
Under 'System Variables' add 2 new vars:
[New]
Var name: DEVMGR_SHOW_DETAILS
Var value: 1
[ok]
[New]
Var name: DEVMGR_SHOW_NONPRESENT_DEVICES
Var value: 1
[ok]
Reboot

 

[A-Mac]

For my correspondents, all. This may be of use to those possessing a
screwdriver and a brave heart, and you can try this at home if you exclude
the kiddies and those with sensitive dispositions.
I decided to sort out a probable h/w problem with the CD drives, so I
re-plugged-in the internal CD drive that came with the pc [replaced because
of its possible s/w problems - no disk or downloads available]; and,
following the instructions, made the 2nd and troublesome drive [the brute
with the Nero disk in its box] Slave and the first one Master (I never knew
what Jumpers were, before). But, the pc & Windows would only recognize
Master; whichever way round I put the Jumpers. Then I remembered that
Start-up was somewhere in the equation, so I unplugged/replugged the hard
drive and then started everything up (I dare not go into what happened when
the rubber band holding in the hd IDE slave connexion burst - it's apparently
supposed to be there).
Anyway, it all works now; with no 3rd party drivers available to either CD
drive. There was a reboot and error at first ("CD has a bad block"), but,
re-installing the drivers from C:/Windows seems to have cleared the decks.
--
Old_and_forgotten

... Device Manager only "sees" things when they are up and running.

Control Panel > System > /Advanced\ [Environment Variables]
Under 'System Variables' add 2 new vars:
[New]
Var name: DEVMGR_SHOW_DETAILS
Var value: 1
[ok]
[New]
Var name: DEVMGR_SHOW_NONPRESENT_DEVICES
Var value: 1
[ok]
Reboot