From: Spiro Trikaliotis on
Hello,

Payton Byrd wrote:

> Groepaz wrote:
>> Wolfgang Moser wrote:
>>
>>> I always thought that Vista won't accepts uncertified
>>> to better say unsigned drivers.
>>
>> afaik they only did that for the 64bit version
>>
> That's correct, however, you can sign the driver yourself.

Yes, if you spend $500 p.a. for the needed VeriSign certificate, you can
sign your driver yourself.

BTW: VeriSign would not give some certificates in some countries. Thus,
if you live in such a country, you're out of the game.

You can use other signed certificates if you run user-mode drivers, but
for kernel-mode drivers, you need a certificate which is allowed by MS.

Regards,
Spiro.

--
Spiro R. Trikaliotis http://opencbm.sf.net/
http://www.trikaliotis.net/ http://www.viceteam.org/
From: Spiro Trikaliotis on
Hello,

Pete Rittwage wrote:

> Sometimes CBM4WIN does something strange where I have to
> uninstall/reinstall the driver.

Hu? Which version do you use? 0.4.0, or some later one?

> No big deal, just power off the drive, do a 'instcbm -r', power on the
> drive, then do 'instcbm' again and it usually comes back to it's
> senses.

Does switched the drive off and on help, too? Or does it help if you do
not switch off the drive, but do instcbm -r & instcbm alone?

THESE are the reports I would like to get to be able to correct the
problems!

Regards,
Spiro.

--
Spiro R. Trikaliotis http://opencbm.sf.net/
http://www.trikaliotis.net/ http://www.viceteam.org/
From: Pete Rittwage on
Spiro Trikaliotis wrote:
> Hello,
>
> Pete Rittwage wrote:
>
>> Sometimes CBM4WIN does something strange where I have to
>> uninstall/reinstall the driver.
>
> Hu? Which version do you use? 0.4.0, or some later one?
>
>> No big deal, just power off the drive, do a 'instcbm -r', power on the
>> drive, then do 'instcbm' again and it usually comes back to it's
>> senses.
>
> Does switched the drive off and on help, too? Or does it help if you do
> not switch off the drive, but do instcbm -r & instcbm alone?
>
> THESE are the reports I would like to get to be able to correct the
> problems!

Hi Spiro,

Sorry, I always figured I was locking up the driver with my MNIB code
since it's constantly under development, so I never mentioned it.


--
-
Pete Rittwage
http://rittwage.com

C64 Preservation Project
http://c64preservation.com
From: Payton Byrd on
Spiro Trikaliotis wrote:
> Hello,
>
> Payton Byrd wrote:
>
>> Groepaz wrote:
>>> Wolfgang Moser wrote:
>>>
>>>> I always thought that Vista won't accepts uncertified
>>>> to better say unsigned drivers.
>>> afaik they only did that for the 64bit version
>>>
>> That's correct, however, you can sign the driver yourself.
>
> Yes, if you spend $500 p.a. for the needed VeriSign certificate, you can
> sign your driver yourself.
>
> BTW: VeriSign would not give some certificates in some countries. Thus,
> if you live in such a country, you're out of the game.
>
> You can use other signed certificates if you run user-mode drivers, but
> for kernel-mode drivers, you need a certificate which is allowed by MS.
>
> Regards,
> Spiro.
>

Did the Daemon Tools guys pay for their cert? I don't think so because
Vista warned me that it was a self-generated certificate. I think they
just made a new certificate using Microsoft's tools and signed the driver.
From: iAN CooG on
Payton Byrd <plbyrd(a)bellsouth.net> wrote:

> Did the Daemon Tools guys pay for their cert? I don't think so
> because Vista warned me that it was a self-generated certificate. I
> think they just made a new certificate using Microsoft's tools and
> signed the driver.

So?

--
-=[]=--- iAN CooG/HokutoForce ---=[]=-
No honey, it's only a computer, PLEASE put down the gun..