unisntall driver for system device CMOS/RTC in windows

Hi all,

I am developing a driver to implement an ISR for demo purposes.
I am planning to use IRQ 8 and the RTC to generate periodic interrupts.

So I need to find a way to prevent system driver cmos/rtc to load at boot in windows 8,
since with the driver loaded I can not access resources reserved by it, like IRQ line 8 ant I/O ports 0x70-71, which I need for my driver.

The problem is:
Windows 8 at boot loads a system driver that reserves this IRQ and can not be disabled.
On the other hand if uninstalled it requires a reboot to complete the uninstall process but at the next boot the driver is loaded again :-(.

I tried to avoid this driver to load at boot commenting lines that refers to it (device id is *PNP0B00) at c:\Windows\Inf\machine.inf

;%*PNP0B00.DeviceDesc% = NO_DRV_X, *PNP0B00 ; Real Time Clock

;*pnp0b00.DeviceDesc=“System CMOS/real time clock”

and then regenerate machine.pnf, but the driver still loads.

Then I also commented on machine.inf_loc:

;*pnp0b00.DeviceDesc=“System CMOS/real time clock”

but the driver still loads :-(.

I also found another instances of these files on other dirs and commented it, but with no luck.

I thought that machine.inf specifies the drivers to load at boot but it seams that do not.
Can anyone tell me what am I missing?

There is another way to prevent a system driver like cmos/rtc to load at boot?

I would appreciate any suggestions on this issue.
Thanks

This is a really bad idea. If you need something for demo purposes get
a demo board, but messing with the real time clock will break Windows.

Don Burn
Windows Filesystem and Driver Consulting
Website: http://www.windrvr.com
Blog: http://msmvps.com/blogs/WinDrvr

“xxxxx@ualg.pt” wrote in message news:xxxxx@ntdev:

> Hi all,
>
> I am developing a driver to implement an ISR for demo purposes.
> I am planning to use IRQ 8 and the RTC to generate periodic interrupts.
>
> So I need to find a way to prevent system driver cmos/rtc to load at boot in windows 8,
> since with the driver loaded I can not access resources reserved by it, like IRQ line 8 ant I/O ports 0x70-71, which I need for my driver.
>
> The problem is:
> Windows 8 at boot loads a system driver that reserves this IRQ and can not be disabled.
> On the other hand if uninstalled it requires a reboot to complete the uninstall process but at the next boot the driver is loaded again :-(.
>
> I tried to avoid this driver to load at boot commenting lines that refers to it (device id is *PNP0B00) at c:\Windows\Inf\machine.inf
>
> ;%*PNP0B00.DeviceDesc% = NO_DRV_X, *PNP0B00 ; Real Time Clock
>
> ;*pnp0b00.DeviceDesc=“System CMOS/real time clock”
>
> and then regenerate machine.pnf, but the driver still loads.
>
> Then I also commented on machine.inf_loc:
>
> ;*pnp0b00.DeviceDesc=“System CMOS/real time clock”
>
> but the driver still loads :-(.
>
> I also found another instances of these files on other dirs and commented it, but with no luck.
>
> I thought that machine.inf specifies the drivers to load at boot but it seams that do not.
> Can anyone tell me what am I missing?
>
> There is another way to prevent a system driver like cmos/rtc to load at boot?
>
> I would appreciate any suggestions on this issue.
> Thanks

Hi Don,

Thanks for the quick reply.

I Thought RTC driver was only required at boot to update system time and at
shutdown to update RTC with current system time.
So I assumed that there is no problem removing the driver while system is
running.

I did the same thing with Linux without problems.
I removed rtc_cmos module, the Linux RTC driver, while system is running
without (at least) visible side effects.

Then I installed a demo driver which implements an IRQ8 ISR.
The driver is fully functional.

This demo program is just for students get used with simple ISR
implementation.
I used RTC in Linux with fair success. Students can test the ISR on any
computer without the need of additional boards.

Now I want to exemplify ISR handling with Windows too.
The porting of the Linux Version for Windows is very straightforward. The
only problem is that I need some device to issue interrupts. If not the RTC
I can use another one, but I would like to use a common device, present in
any computer, so that students do not need to get additional hardware.

On 25 May 2013 13:49, Don Burn wrote:

> This is a really bad idea. If you need something for demo purposes get a
> demo board, but messing with the real time clock will break Windows.
>
>
> Don Burn
> Windows Filesystem and Driver Consulting
> Website: http://www.windrvr.com
> Blog: http://msmvps.com/blogs/**WinDrvr http:
>
>
>
> “xxxxx@ualg.pt” wrote in message news:xxxxx@ntdev:
>
>
> Hi all,
>>
>> I am developing a driver to implement an ISR for demo purposes.
>> I am planning to use IRQ 8 and the RTC to generate periodic interrupts.
>>
>> So I need to find a way to prevent system driver cmos/rtc to load at
>> boot in windows 8,
>> since with the driver loaded I can not access resources reserved by it,
>> like IRQ line 8 ant I/O ports 0x70-71, which I need for my driver.
>>
>> The problem is:
>> Windows 8 at boot loads a system driver that reserves this IRQ and can
>> not be disabled.
>> On the other hand if uninstalled it requires a reboot to complete the
>> uninstall process but at the next boot the driver is loaded again :-(.
>>
>> I tried to avoid this driver to load at boot commenting lines that refers
>> to it (device id is *PNP0B00) at c:\Windows\Inf\machine.inf
>>
>> ;%*PNP0B00.DeviceDesc% = NO_DRV_X, *PNP0B00 ; Real Time Clock
>>
>> ;*pnp0b00.DeviceDesc=“System CMOS/real time clock”
>>
>> and then regenerate machine.pnf, but the driver still loads.
>>
>> Then I also commented on machine.inf_loc:
>>
>> ;*pnp0b00.DeviceDesc=“System CMOS/real time clock”
>>
>> but the driver still loads :-(.
>>
>> I also found another instances of these files on other dirs and commented
>> it, but with no luck.
>>
>> I thought that machine.inf specifies the drivers to load at boot but it
>> seams that do not.
>> Can anyone tell me what am I missing?
>>
>> There is another way to prevent a system driver like cmos/rtc to load at
>> boot?
>>
>> I would appreciate any suggestions on this issue.
>> Thanks
>>
>
>
> —
> NTDEV is sponsored by OSR
>
> OSR is HIRING!! See http://www.osr.com/careers
>
> For our schedule of WDF, WDM, debugging and other seminars visit:
> http://www.osr.com/seminars
>
> To unsubscribe, visit the List Server section of OSR Online at
> http://www.osronline.com/page.**cfm?name=ListServerhttp:
>
>


Helder Daniel
UALG - FCT
DEEI

http://w3.ualg.pt/~hdaniel</http:></http:>

>I did the same thing with Linux without problems.

This is because Linux does not use RTC and, instead, relies upon IRQ0 timer that may be either HPET or PIT if your motherboard is an ancient one. You can run cat /proc/interrupts if you don’t believe me…

However, Windows uses RTC. Therefore, if you attempt the same thing with Windows you will most definitely break the system…

Anton Bassov

Some years ago, we did a device simulator. We had a process that called
int n, where n was the desired interrupt. It worked just fine as long as
you had the multiprocessor HAL installed. These days, I don’t know of any
machine that has the uniprocessor HAL. So just write a program that
issues an int n instruction for whatever n you want, and run it. There is
no need to replace an existing driver to do this.
joe

Hi Don,

Thanks for the quick reply.

I Thought RTC driver was only required at boot to update system time and
at
shutdown to update RTC with current system time.
So I assumed that there is no problem removing the driver while system is
running.

I did the same thing with Linux without problems.
I removed rtc_cmos module, the Linux RTC driver, while system is running
without (at least) visible side effects.

Then I installed a demo driver which implements an IRQ8 ISR.
The driver is fully functional.

This demo program is just for students get used with simple ISR
implementation.
I used RTC in Linux with fair success. Students can test the ISR on any
computer without the need of additional boards.

Now I want to exemplify ISR handling with Windows too.
The porting of the Linux Version for Windows is very straightforward. The
only problem is that I need some device to issue interrupts. If not the
RTC
I can use another one, but I would like to use a common device, present in
any computer, so that students do not need to get additional hardware.

On 25 May 2013 13:49, Don Burn wrote:
>
>> This is a really bad idea. If you need something for demo purposes get
>> a
>> demo board, but messing with the real time clock will break Windows.
>>
>>
>> Don Burn
>> Windows Filesystem and Driver Consulting
>> Website: http://www.windrvr.com
>> Blog: http://msmvps.com/blogs/**WinDrvr
>> http:
>>
>>
>>
>> “xxxxx@ualg.pt” wrote in message news:xxxxx@ntdev:
>>
>>
>> Hi all,
>>>
>>> I am developing a driver to implement an ISR for demo purposes.
>>> I am planning to use IRQ 8 and the RTC to generate periodic interrupts.
>>>
>>> So I need to find a way to prevent system driver cmos/rtc to load at
>>> boot in windows 8,
>>> since with the driver loaded I can not access resources reserved by it,
>>> like IRQ line 8 ant I/O ports 0x70-71, which I need for my driver.
>>>
>>> The problem is:
>>> Windows 8 at boot loads a system driver that reserves this IRQ and can
>>> not be disabled.
>>> On the other hand if uninstalled it requires a reboot to complete the
>>> uninstall process but at the next boot the driver is loaded again :-(.
>>>
>>> I tried to avoid this driver to load at boot commenting lines that
>>> refers
>>> to it (device id is *PNP0B00) at c:\Windows\Inf\machine.inf
>>>
>>> ;%*PNP0B00.DeviceDesc% = NO_DRV_X, *PNP0B00 ; Real Time Clock
>>>
>>> ;*pnp0b00.DeviceDesc=“System CMOS/real time clock”
>>>
>>> and then regenerate machine.pnf, but the driver still loads.
>>>
>>> Then I also commented on machine.inf_loc:
>>>
>>> ;*pnp0b00.DeviceDesc=“System CMOS/real time clock”
>>>
>>> but the driver still loads :-(.
>>>
>>> I also found another instances of these files on other dirs and
>>> commented
>>> it, but with no luck.
>>>
>>> I thought that machine.inf specifies the drivers to load at boot but it
>>> seams that do not.
>>> Can anyone tell me what am I missing?
>>>
>>> There is another way to prevent a system driver like cmos/rtc to load
>>> at
>>> boot?
>>>
>>> I would appreciate any suggestions on this issue.
>>> Thanks
>>>
>>
>>
>> —
>> NTDEV is sponsored by OSR
>>
>> OSR is HIRING!! See http://www.osr.com/careers
>>
>> For our schedule of WDF, WDM, debugging and other seminars visit:
>> http://www.osr.com/seminars
>>
>> To unsubscribe, visit the List Server section of OSR Online at
>> http://www.osronline.com/page.**cfm?name=ListServerhttp:
>>
>>
>
>
> –
> Helder Daniel
> UALG - FCT
> DEEI
>
> http://w3.ualg.pt/~hdaniel
>
> —
> NTDEV is sponsored by OSR
>
> OSR is HIRING!! See http://www.osr.com/careers
>
> For our schedule of WDF, WDM, debugging and other seminars visit:
> http://www.osr.com/seminars
>
> To unsubscribe, visit the List Server section of OSR Online at
> http://www.osronline.com/page.cfm?name=ListServer</http:></http:>

Hi Anton

Thanks for your explanation.
I have no problem believing your explanation, however
I did not understood how /proc/interrupts shows me that the RTC is not used
by Linux.

If I ran cat /proc/interrupts it just shows IRQ0 line in use by
timer and 8 by rtc1 (it does not metion rtc_cmos module):

xxxxx@debian:~$ cat /proc/interrupts
CPU0
0: 623 IO-APIC-edge timer
1: 23759 IO-APIC-edge i8042
6: 3 IO-APIC-edge floppy
7: 0 IO-APIC-edge parport0
8: 2 IO-APIC-edge rtc1
9: 0 IO-APIC-fasteoi acpi
12: 489932 IO-APIC-edge i8042
14: 0 IO-APIC-edge ide0
15: 1779268 IO-APIC-edge ide1

On 25 May 2013 17:26, wrote:

> >I did the same thing with Linux without problems.
>
>
>
> This is because Linux does not use RTC and, instead, relies upon IRQ0
> timer that may be either HPET or PIT if your motherboard is an ancient one.
> You can run cat /proc/interrupts if you don’t believe me…
>
> However, Windows uses RTC. Therefore, if you attempt the same thing with
> Windows you will most definitely break the system…
>
>
> Anton Bassov
>
> —
> NTDEV is sponsored by OSR
>
> OSR is HIRING!! See http://www.osr.com/careers
>
> For our schedule of WDF, WDM, debugging and other seminars visit:
> http://www.osr.com/seminars
>
> To unsubscribe, visit the List Server section of OSR Online at
> http://www.osronline.com/page.cfm?name=ListServer
>
>


Helder Daniel
UALG - FCT
DEEI

http://w3.ualg.pt/~hdaniel

Hi newcomer,

Thank four your suggestion.

I tried that too as an alternative. I tried in a user space program to
issue an int mnemonic (I am using Windows 8 64 bits):

int _tmain(int argc, _TCHAR* argv) {
_asm { int 0x8 }
}

But even running it as administrator It gives me an exception:

Unhandled exception at 0x00B514D5 in issueInt.exe: 0xC0000005: Access
violation reading location 0xFFFFFFFF.

I tried the instruction int with other arguments than 8. Tried with free
IRQ lines (checked on device manager some free IRQ lines) but it gives me
the same exception.

I am not sure if the argument of int is the IRQ line, maybe its the entry
in the IDT?
I tried with some other values but still have the exception.
Can you tell me what argument you used in your program?

On the other hand maybe the system prevents issue soft interrupts from user
space. (The syscalls now are not called using int but SYSENTER mnemonic…)?

If I tried to do that in a kernel mode driver compiler won’t let me compile
it, giving error:

error C4235: nonstandard extension used : ‘_asm’ keyword not supported on
this architecture

On 25 May 2013 17:34, wrote:

> Some years ago, we did a device simulator. We had a process that called
> int n, where n was the desired interrupt. It worked just fine as long as
> you had the multiprocessor HAL installed. These days, I don’t know of any
> machine that has the uniprocessor HAL. So just write a program that
> issues an int n instruction for whatever n you want, and run it. There is
> no need to replace an existing driver to do this.
> joe
>
> > Hi Don,
> >
> > Thanks for the quick reply.
> >
> > I Thought RTC driver was only required at boot to update system time and
> > at
> > shutdown to update RTC with current system time.
> > So I assumed that there is no problem removing the driver while system is
> > running.
> >
> > I did the same thing with Linux without problems.
> > I removed rtc_cmos module, the Linux RTC driver, while system is running
> > without (at least) visible side effects.
> >
> > Then I installed a demo driver which implements an IRQ8 ISR.
> > The driver is fully functional.
> >
> > This demo program is just for students get used with simple ISR
> > implementation.
> > I used RTC in Linux with fair success. Students can test the ISR on any
> > computer without the need of additional boards.
> >
> > Now I want to exemplify ISR handling with Windows too.
> > The porting of the Linux Version for Windows is very straightforward. The
> > only problem is that I need some device to issue interrupts. If not the
> > RTC
> > I can use another one, but I would like to use a common device, present
> in
> > any computer, so that students do not need to get additional hardware.
> >
> >
> >
> >
> >
> > On 25 May 2013 13:49, Don Burn wrote:
> >
> >> This is a really bad idea. If you need something for demo purposes get
> >> a
> >> demo board, but messing with the real time clock will break Windows.
> >>
> >>
> >> Don Burn
> >> Windows Filesystem and Driver Consulting
> >> Website: http://www.windrvr.com
> >> Blog: http://msmvps.com/blogs/**WinDrvr
> >> http:
> >>
> >>
> >>
> >> “xxxxx@ualg.pt” wrote in message news:xxxxx@ntdev:
> >>
> >>
> >> Hi all,
> >>>
> >>> I am developing a driver to implement an ISR for demo purposes.
> >>> I am planning to use IRQ 8 and the RTC to generate periodic interrupts.
> >>>
> >>> So I need to find a way to prevent system driver cmos/rtc to load at
> >>> boot in windows 8,
> >>> since with the driver loaded I can not access resources reserved by it,
> >>> like IRQ line 8 ant I/O ports 0x70-71, which I need for my driver.
> >>>
> >>> The problem is:
> >>> Windows 8 at boot loads a system driver that reserves this IRQ and can
> >>> not be disabled.
> >>> On the other hand if uninstalled it requires a reboot to complete the
> >>> uninstall process but at the next boot the driver is loaded again :-(.
> >>>
> >>> I tried to avoid this driver to load at boot commenting lines that
> >>> refers
> >>> to it (device id is *PNP0B00) at c:\Windows\Inf\machine.inf
> >>>
> >>> ;%*PNP0B00.DeviceDesc% = NO_DRV_X, *PNP0B00 ; Real Time Clock
> >>>
> >>> ;*pnp0b00.DeviceDesc=“System CMOS/real time clock”
> >>>
> >>> and then regenerate machine.pnf, but the driver still loads.
> >>>
> >>> Then I also commented on machine.inf_loc:
> >>>
> >>> ;*pnp0b00.DeviceDesc=“System CMOS/real time clock”
> >>>
> >>> but the driver still loads :-(.
> >>>
> >>> I also found another instances of these files on other dirs and
> >>> commented
> >>> it, but with no luck.
> >>>
> >>> I thought that machine.inf specifies the drivers to load at boot but it
> >>> seams that do not.
> >>> Can anyone tell me what am I missing?
> >>>
> >>> There is another way to prevent a system driver like cmos/rtc to load
> >>> at
> >>> boot?
> >>>
> >>> I would appreciate any suggestions on this issue.
> >>> Thanks
> >>>
> >>
> >>
> >> —
> >> NTDEV is sponsored by OSR
> >>
> >> OSR is HIRING!! See http://www.osr.com/careers
> >>
> >> For our schedule of WDF, WDM, debugging and other seminars visit:
> >> http://www.osr.com/seminars
> >>
> >> To unsubscribe, visit the List Server section of OSR Online at
> >> http://www.osronline.com/page.**cfm?name=ListServer&lt;
> http://www.osronline.com/page.cfm?name=ListServer&gt;
> >>
> >>
> >
> >
> > –
> > Helder Daniel
> > UALG - FCT
> > DEEI
> >
> > http://w3.ualg.pt/~hdaniel
> >
> > —
> > NTDEV is sponsored by OSR
> >
> > OSR is HIRING!! See http://www.osr.com/careers
> >
> > For our schedule of WDF, WDM, debugging and other seminars visit:
> > http://www.osr.com/seminars
> >
> > To unsubscribe, visit the List Server section of OSR Online at
> > http://www.osronline.com/page.cfm?name=ListServer
>
>
>
> —
> NTDEV is sponsored by OSR
>
> OSR is HIRING!! See http://www.osr.com/careers
>
> For our schedule of WDF, WDM, debugging and other seminars visit:
> http://www.osr.com/seminars
>
> To unsubscribe, visit the List Server section of OSR Online at
> http://www.osronline.com/page.cfm?name=ListServer
>
>


Helder Daniel
UALG - FCT
DEEI

http://w3.ualg.pt/~hdaniel</http:>

> Hi newcomer,

Thank four your suggestion.

I tried that too as an alternative. I tried in a user space program to
issue an int mnemonic (I am using Windows 8 64 bits):

int _tmain(int argc, _TCHAR* argv) {
_asm { int 0x8 }
}

But even running it as administrator It gives me an exception:

Unhandled exception at 0x00B514D5 in issueInt.exe: 0xC0000005: Access
violation reading location 0xFFFFFFFF.
***
Our code ran on Win32. The 64-bit compiler does not support __asm and
instead there are a set of “compiler intrinsics” you use instread.

Sounds like someone has fixed a “hole” in Windows but as to why you see
access denied instead of illegal instruction is a bit of a mystery.
joe
***

I tried the instruction int with other arguments than 8. Tried with free
IRQ lines (checked on device manager some free IRQ lines) but it gives me
the same exception.

I am not sure if the argument of int is the IRQ line, maybe its the entry
in the IDT?
I tried with some other values but still have the exception.
Can you tell me what argument you used in your program?

On the other hand maybe the system prevents issue soft interrupts from
user
space. (The syscalls now are not called using int but SYSENTER
mnemonic…)?

If I tried to do that in a kernel mode driver compiler won’t let me
compile
it, giving error:

error C4235: nonstandard extension used : ‘_asm’ keyword not supported on
this architecture

On 25 May 2013 17:34, wrote:
>
>> Some years ago, we did a device simulator. We had a process that called
>> int n, where n was the desired interrupt. It worked just fine as long
>> as
>> you had the multiprocessor HAL installed. These days, I don’t know of
>> any
>> machine that has the uniprocessor HAL. So just write a program that
>> issues an int n instruction for whatever n you want, and run it. There
>> is
>> no need to replace an existing driver to do this.
>> joe
>>
>> > Hi Don,
>> >
>> > Thanks for the quick reply.
>> >
>> > I Thought RTC driver was only required at boot to update system time
>> and
>> > at
>> > shutdown to update RTC with current system time.
>> > So I assumed that there is no problem removing the driver while system
>> is
>> > running.
>> >
>> > I did the same thing with Linux without problems.
>> > I removed rtc_cmos module, the Linux RTC driver, while system is
>> running
>> > without (at least) visible side effects.
>> >
>> > Then I installed a demo driver which implements an IRQ8 ISR.
>> > The driver is fully functional.
>> >
>> > This demo program is just for students get used with simple ISR
>> > implementation.
>> > I used RTC in Linux with fair success. Students can test the ISR on
>> any
>> > computer without the need of additional boards.
>> >
>> > Now I want to exemplify ISR handling with Windows too.
>> > The porting of the Linux Version for Windows is very straightforward.
>> The
>> > only problem is that I need some device to issue interrupts. If not
>> the
>> > RTC
>> > I can use another one, but I would like to use a common device,
>> present
>> in
>> > any computer, so that students do not need to get additional hardware.
>> >
>> >
>> >
>> >
>> >
>> > On 25 May 2013 13:49, Don Burn wrote:
>> >
>> >> This is a really bad idea. If you need something for demo purposes
>> get
>> >> a
>> >> demo board, but messing with the real time clock will break Windows.
>> >>
>> >>
>> >> Don Burn
>> >> Windows Filesystem and Driver Consulting
>> >> Website: http://www.windrvr.com
>> >> Blog: http://msmvps.com/blogs/**WinDrvr
>> >> http:
>> >>
>> >>
>> >>
>> >> “xxxxx@ualg.pt” wrote in message
>> news:xxxxx@ntdev:
>> >>
>> >>
>> >> Hi all,
>> >>>
>> >>> I am developing a driver to implement an ISR for demo purposes.
>> >>> I am planning to use IRQ 8 and the RTC to generate periodic
>> interrupts.
>> >>>
>> >>> So I need to find a way to prevent system driver cmos/rtc to load
>> at
>> >>> boot in windows 8,
>> >>> since with the driver loaded I can not access resources reserved by
>> it,
>> >>> like IRQ line 8 ant I/O ports 0x70-71, which I need for my driver.
>> >>>
>> >>> The problem is:
>> >>> Windows 8 at boot loads a system driver that reserves this IRQ and
>> can
>> >>> not be disabled.
>> >>> On the other hand if uninstalled it requires a reboot to complete
>> the
>> >>> uninstall process but at the next boot the driver is loaded again
>> :-(.
>> >>>
>> >>> I tried to avoid this driver to load at boot commenting lines that
>> >>> refers
>> >>> to it (device id is *PNP0B00) at c:\Windows\Inf\machine.inf
>> >>>
>> >>> ;%*PNP0B00.DeviceDesc% = NO_DRV_X, *PNP0B00 ; Real Time
>> Clock
>> >>>
>> >>> ;*pnp0b00.DeviceDesc=“System CMOS/real time clock”
>> >>>
>> >>> and then regenerate machine.pnf, but the driver still loads.
>> >>>
>> >>> Then I also commented on machine.inf_loc:
>> >>>
>> >>> ;*pnp0b00.DeviceDesc=“System CMOS/real time clock”
>> >>>
>> >>> but the driver still loads :-(.
>> >>>
>> >>> I also found another instances of these files on other dirs and
>> >>> commented
>> >>> it, but with no luck.
>> >>>
>> >>> I thought that machine.inf specifies the drivers to load at boot but
>> it
>> >>> seams that do not.
>> >>> Can anyone tell me what am I missing?
>> >>>
>> >>> There is another way to prevent a system driver like cmos/rtc to
>> load
>> >>> at
>> >>> boot?
>> >>>
>> >>> I would appreciate any suggestions on this issue.
>> >>> Thanks
>> >>>
>> >>
>> >>
>> >> —
>> >> NTDEV is sponsored by OSR
>> >>
>> >> OSR is HIRING!! See http://www.osr.com/careers
>> >>
>> >> For our schedule of WDF, WDM, debugging and other seminars visit:
>> >> http://www.osr.com/seminars
>> >>
>> >> To unsubscribe, visit the List Server section of OSR Online at
>> >> http://www.osronline.com/page.**cfm?name=ListServer&lt;
>> http://www.osronline.com/page.cfm?name=ListServer&gt;
>> >>
>> >>
>> >
>> >
>> > –
>> > Helder Daniel
>> > UALG - FCT
>> > DEEI
>> >
>> > http://w3.ualg.pt/~hdaniel
>> >
>> > —
>> > NTDEV is sponsored by OSR
>> >
>> > OSR is HIRING!! See http://www.osr.com/careers
>> >
>> > For our schedule of WDF, WDM, debugging and other seminars visit:
>> > http://www.osr.com/seminars
>> >
>> > To unsubscribe, visit the List Server section of OSR Online at
>> > http://www.osronline.com/page.cfm?name=ListServer
>>
>>
>>
>> —
>> NTDEV is sponsored by OSR
>>
>> OSR is HIRING!! See http://www.osr.com/careers
>>
>> For our schedule of WDF, WDM, debugging and other seminars visit:
>> http://www.osr.com/seminars
>>
>> To unsubscribe, visit the List Server section of OSR Online at
>> http://www.osronline.com/page.cfm?name=ListServer
>>
>>
>
>
> –
> Helder Daniel
> UALG - FCT
> DEEI
>
> http://w3.ualg.pt/~hdaniel
>
> —
> NTDEV is sponsored by OSR
>
> OSR is HIRING!! See http://www.osr.com/careers
>
> For our schedule of WDF, WDM, debugging and other seminars visit:
> http://www.osr.com/seminars
>
> To unsubscribe, visit the List Server section of OSR Online at
> http://www.osronline.com/page.cfm?name=ListServer</http:>

In general if the OS has grabbed a resource you can’t use it. Joe was
referring to an old device simulator that he and Ed Dekker did, you can
find the sources at
http://www.eclectic-eng.com/downloadableFiles/SimulatorAndDriver.zip
This may or may not work, but at least would be a possible starting
point. Your code is a user space program, which is not going to be able
to handle an INT instruction like that.

Don Burn
Windows Filesystem and Driver Consulting
Website: http://www.windrvr.com
Blog: http://msmvps.com/blogs/WinDrvr

“Helder Daniel” wrote in message news:xxxxx@ntdev:

> Hi newcomer,
>
> Thank four your suggestion.
>
> I tried that too as an alternative. I tried in a user space program to
> issue an int mnemonic (I am using Windows 8 64 bits):
>
> int _tmain(int argc, _TCHAR* argv) {
> _asm { int 0x8 }
> }
>
> But even running it as administrator It gives me an exception:
>
> Unhandled exception at 0x00B514D5 in issueInt.exe: 0xC0000005: Access
> violation reading location 0xFFFFFFFF.
>
> I tried the instruction int with other arguments than 8. Tried with free
> IRQ lines (checked on device manager some free IRQ lines) but it gives me
> the same exception.
>
> I am not sure if the argument of int is the IRQ line, maybe its the entry
> in the IDT?
> I tried with some other values but still have the exception.
> Can you tell me what argument you used in your program?
>
> On the other hand maybe the system prevents issue soft interrupts from user
> space. (The syscalls now are not called using int but SYSENTER mnemonic…)?
>
> If I tried to do that in a kernel mode driver compiler won’t let me compile
> it, giving error:
>
> error C4235: nonstandard extension used : ‘_asm’ keyword not supported on
> this architecture
>
>
>
> On 25 May 2013 17:34, wrote:
>
> > Some years ago, we did a device simulator. We had a process that called
> > int n, where n was the desired interrupt. It worked just fine as long as
> > you had the multiprocessor HAL installed. These days, I don’t know of any
> > machine that has the uniprocessor HAL. So just write a program that
> > issues an int n instruction for whatever n you want, and run it. There is
> > no need to replace an existing driver to do this.
> > joe
> >
> > > Hi Don,
> > >
> > > Thanks for the quick reply.
> > >
> > > I Thought RTC driver was only required at boot to update system time and
> > > at
> > > shutdown to update RTC with current system time.
> > > So I assumed that there is no problem removing the driver while system is
> > > running.
> > >
> > > I did the same thing with Linux without problems.
> > > I removed rtc_cmos module, the Linux RTC driver, while system is running
> > > without (at least) visible side effects.
> > >
> > > Then I installed a demo driver which implements an IRQ8 ISR.
> > > The driver is fully functional.
> > >
> > > This demo program is just for students get used with simple ISR
> > > implementation.
> > > I used RTC in Linux with fair success. Students can test the ISR on any
> > > computer without the need of additional boards.
> > >
> > > Now I want to exemplify ISR handling with Windows too.
> > > The porting of the Linux Version for Windows is very straightforward. The
> > > only problem is that I need some device to issue interrupts. If not the
> > > RTC
> > > I can use another one, but I would like to use a common device, present
> > in
> > > any computer, so that students do not need to get additional hardware.
> > >
> > >
> > >
> > >
> > >
> > > On 25 May 2013 13:49, Don Burn wrote:
> > >
> > >> This is a really bad idea. If you need something for demo purposes get
> > >> a
> > >> demo board, but messing with the real time clock will break Windows.
> > >>
> > >>
> > >> Don Burn
> > >> Windows Filesystem and Driver Consulting
> > >> Website: http://www.windrvr.com
> > >> Blog: http://msmvps.com/blogs/**WinDrvr
> > >> http:
> > >>
> > >>
> > >>
> > >> “xxxxx@ualg.pt” wrote in message news:xxxxx@ntdev:
> > >>
> > >>
> > >> Hi all,
> > >>>
> > >>> I am developing a driver to implement an ISR for demo purposes.
> > >>> I am planning to use IRQ 8 and the RTC to generate periodic interrupts.
> > >>>
> > >>> So I need to find a way to prevent system driver cmos/rtc to load at
> > >>> boot in windows 8,
> > >>> since with the driver loaded I can not access resources reserved by it,
> > >>> like IRQ line 8 ant I/O ports 0x70-71, which I need for my driver.
> > >>>
> > >>> The problem is:
> > >>> Windows 8 at boot loads a system driver that reserves this IRQ and can
> > >>> not be disabled.
> > >>> On the other hand if uninstalled it requires a reboot to complete the
> > >>> uninstall process but at the next boot the driver is loaded again :-(.
> > >>>
> > >>> I tried to avoid this driver to load at boot commenting lines that
> > >>> refers
> > >>> to it (device id is *PNP0B00) at c:\Windows\Inf\machine.inf
> > >>>
> > >>> ;%*PNP0B00.DeviceDesc% = NO_DRV_X, *PNP0B00 ; Real Time Clock
> > >>>
> > >>> ;*pnp0b00.DeviceDesc=“System CMOS/real time clock”
> > >>>
> > >>> and then regenerate machine.pnf, but the driver still loads.
> > >>>
> > >>> Then I also commented on machine.inf_loc:
> > >>>
> > >>> ;*pnp0b00.DeviceDesc=“System CMOS/real time clock”
> > >>>
> > >>> but the driver still loads :-(.
> > >>>
> > >>> I also found another instances of these files on other dirs and
> > >>> commented
> > >>> it, but with no luck.
> > >>>
> > >>> I thought that machine.inf specifies the drivers to load at boot but it
> > >>> seams that do not.
> > >>> Can anyone tell me what am I missing?
> > >>>
> > >>> There is another way to prevent a system driver like cmos/rtc to load
> > >>> at
> > >>> boot?
> > >>>
> > >>> I would appreciate any suggestions on this issue.
> > >>> Thanks
> > >>>
> > >>
> > >>
> > >> —
> > >> NTDEV is sponsored by OSR
> > >>
> > >> OSR is HIRING!! See http://www.osr.com/careers
> > >>
> > >> For our schedule of WDF, WDM, debugging and other seminars visit:
> > >> http://www.osr.com/seminars
> > >>
> > >> To unsubscribe, visit the List Server section of OSR Online at
> > >> http://www.osronline.com/page.**cfm?name=ListServer&lt;
> > http://www.osronline.com/page.cfm?name=ListServer&gt;
> > >>
> > >>
> > >
> > >
> > > –
> > > Helder Daniel
> > > UALG - FCT
> > > DEEI
> > >
> > > http://w3.ualg.pt/~hdaniel
> > >
> > > —
> > > NTDEV is sponsored by OSR
> > >
> > > OSR is HIRING!! See http://www.osr.com/careers
> > >
> > > For our schedule of WDF, WDM, debugging and other seminars visit:
> > > http://www.osr.com/seminars
> > >
> > > To unsubscribe, visit the List Server section of OSR Online at
> > > http://www.osronline.com/page.cfm?name=ListServer
> >
> >
> >
> > —
> > NTDEV is sponsored by OSR
> >
> > OSR is HIRING!! See http://www.osr.com/careers
> >
> > For our schedule of WDF, WDM, debugging and other seminars visit:
> > http://www.osr.com/seminars
> >
> > To unsubscribe, visit the List Server section of OSR Online at
> > http://www.osronline.com/page.cfm?name=ListServer
> >
> >
>
>
> –
> Helder Daniel
> UALG - FCT
> DEEI
>
> http://w3.ualg.pt/~hdaniel</http:>

> If I ran cat /proc/interrupts it just shows IRQ0 line in use by timer and 8 by rtc1 (it does not

metion rtc_cmos module):

What about the second column in a table? Does not it suggest anything to you???

Anton Bassov

Hi Joe,

Thanks for the suggestion of compiler intrinsics.
However I didn’t find any function to issue a specified interrupt.
Just int2e to issue syscalls and _debugbreak to issue int 3.

My first thought was access violation to some protected resources like some
interrupt vectors.
But you’re right INT can be an illegal instruction in user mode.
I did not think about that because of the old kernel mode entering way
issuing int 2E.

On 25 May 2013 21:10, wrote:

> > Hi newcomer,
> >
> > Thank four your suggestion.
> >
> > I tried that too as an alternative. I tried in a user space program to
> > issue an int mnemonic (I am using Windows 8 64 bits):
> >
> > int _tmain(int argc, _TCHAR* argv) {
> > _asm { int 0x8 }
> > }
> >
> > But even running it as administrator It gives me an exception:
> >
> > Unhandled exception at 0x00B514D5 in issueInt.exe: 0xC0000005: Access
> > violation reading location 0xFFFFFFFF.
>
> Our code ran on Win32. The 64-bit compiler does not support __asm and
> instead there are a set of “compiler intrinsics” you use instread.
>
> Sounds like someone has fixed a “hole” in Windows but as to why you see
> access denied instead of illegal instruction is a bit of a mystery.
> joe
>

> >
> > I tried the instruction int with other arguments than 8. Tried with free
> > IRQ lines (checked on device manager some free IRQ lines) but it gives me
> > the same exception.
> >
> > I am not sure if the argument of int is the IRQ line, maybe its the entry
> > in the IDT?
> > I tried with some other values but still have the exception.
> > Can you tell me what argument you used in your program?
> >
> > On the other hand maybe the system prevents issue soft interrupts from
> > user
> > space. (The syscalls now are not called using int but SYSENTER
> > mnemonic…)?
> >
> > If I tried to do that in a kernel mode driver compiler won’t let me
> > compile
> > it, giving error:
> >
> > error C4235: nonstandard extension used : ‘_asm’ keyword not supported on
> > this architecture
> >
> >
> >
> > On 25 May 2013 17:34, wrote:
> >
> >> Some years ago, we did a device simulator. We had a process that called
> >> int n, where n was the desired interrupt. It worked just fine as long
> >> as
> >> you had the multiprocessor HAL installed. These days, I don’t know of
> >> any
> >> machine that has the uniprocessor HAL. So just write a program that
> >> issues an int n instruction for whatever n you want, and run it. There
> >> is
> >> no need to replace an existing driver to do this.
> >> joe
> >>
> >> > Hi Don,
> >> >
> >> > Thanks for the quick reply.
> >> >
> >> > I Thought RTC driver was only required at boot to update system time
> >> and
> >> > at
> >> > shutdown to update RTC with current system time.
> >> > So I assumed that there is no problem removing the driver while system
> >> is
> >> > running.
> >> >
> >> > I did the same thing with Linux without problems.
> >> > I removed rtc_cmos module, the Linux RTC driver, while system is
> >> running
> >> > without (at least) visible side effects.
> >> >
> >> > Then I installed a demo driver which implements an IRQ8 ISR.
> >> > The driver is fully functional.
> >> >
> >> > This demo program is just for students get used with simple ISR
> >> > implementation.
> >> > I used RTC in Linux with fair success. Students can test the ISR on
> >> any
> >> > computer without the need of additional boards.
> >> >
> >> > Now I want to exemplify ISR handling with Windows too.
> >> > The porting of the Linux Version for Windows is very straightforward.
> >> The
> >> > only problem is that I need some device to issue interrupts. If not
> >> the
> >> > RTC
> >> > I can use another one, but I would like to use a common device,
> >> present
> >> in
> >> > any computer, so that students do not need to get additional hardware.
> >> >
> >> >
> >> >
> >> >
> >> >
> >> > On 25 May 2013 13:49, Don Burn wrote:
> >> >
> >> >> This is a really bad idea. If you need something for demo purposes
> >> get
> >> >> a
> >> >> demo board, but messing with the real time clock will break Windows.
> >> >>
> >> >>
> >> >> Don Burn
> >> >> Windows Filesystem and Driver Consulting
> >> >> Website: http://www.windrvr.com
> >> >> Blog: http://msmvps.com/blogs/**WinDrvr
> >> >> http:
> >> >>
> >> >>
> >> >>
> >> >> “xxxxx@ualg.pt” wrote in message
> >> news:xxxxx@ntdev:
> >> >>
> >> >>
> >> >> Hi all,
> >> >>>
> >> >>> I am developing a driver to implement an ISR for demo purposes.
> >> >>> I am planning to use IRQ 8 and the RTC to generate periodic
> >> interrupts.
> >> >>>
> >> >>> So I need to find a way to prevent system driver cmos/rtc to load
> >> at
> >> >>> boot in windows 8,
> >> >>> since with the driver loaded I can not access resources reserved by
> >> it,
> >> >>> like IRQ line 8 ant I/O ports 0x70-71, which I need for my driver.
> >> >>>
> >> >>> The problem is:
> >> >>> Windows 8 at boot loads a system driver that reserves this IRQ and
> >> can
> >> >>> not be disabled.
> >> >>> On the other hand if uninstalled it requires a reboot to complete
> >> the
> >> >>> uninstall process but at the next boot the driver is loaded again
> >> :-(.
> >> >>>
> >> >>> I tried to avoid this driver to load at boot commenting lines that
> >> >>> refers
> >> >>> to it (device id is *PNP0B00) at c:\Windows\Inf\machine.inf
> >> >>>
> >> >>> ;%*PNP0B00.DeviceDesc% = NO_DRV_X, *PNP0B00 ; Real Time
> >> Clock
> >> >>>
> >> >>> ;*pnp0b00.DeviceDesc=“System CMOS/real time clock”
> >> >>>
> >> >>> and then regenerate machine.pnf, but the driver still loads.
> >> >>>
> >> >>> Then I also commented on machine.inf_loc:
> >> >>>
> >> >>> ;*pnp0b00.DeviceDesc=“System CMOS/real time clock”
> >> >>>
> >> >>> but the driver still loads :-(.
> >> >>>
> >> >>> I also found another instances of these files on other dirs and
> >> >>> commented
> >> >>> it, but with no luck.
> >> >>>
> >> >>> I thought that machine.inf specifies the drivers to load at boot but
> >> it
> >> >>> seams that do not.
> >> >>> Can anyone tell me what am I missing?
> >> >>>
> >> >>> There is another way to prevent a system driver like cmos/rtc to
> >> load
> >> >>> at
> >> >>> boot?
> >> >>>
> >> >>> I would appreciate any suggestions on this issue.
> >> >>> Thanks
> >> >>>
> >> >>
> >> >>
> >> >> —
> >> >> NTDEV is sponsored by OSR
> >> >>
> >> >> OSR is HIRING!! See http://www.osr.com/careers
> >> >>
> >> >> For our schedule of WDF, WDM, debugging and other seminars visit:
> >> >> http://www.osr.com/seminars
> >> >>
> >> >> To unsubscribe, visit the List Server section of OSR Online at
> >> >> http://www.osronline.com/page.**cfm?name=ListServer&lt;
> >> http://www.osronline.com/page.cfm?name=ListServer&gt;
> >> >>
> >> >>
> >> >
> >> >
> >> > –
> >> > Helder Daniel
> >> > UALG - FCT
> >> > DEEI
> >> >
> >> > http://w3.ualg.pt/~hdaniel
> >> >
> >> > —
> >> > NTDEV is sponsored by OSR
> >> >
> >> > OSR is HIRING!! See http://www.osr.com/careers
> >> >
> >> > For our schedule of WDF, WDM, debugging and other seminars visit:
> >> > http://www.osr.com/seminars
> >> >
> >> > To unsubscribe, visit the List Server section of OSR Online at
> >> > http://www.osronline.com/page.cfm?name=ListServer
> >>
> >>
> >>
> >> —
> >> NTDEV is sponsored by OSR
> >>
> >> OSR is HIRING!! See http://www.osr.com/careers
> >>
> >> For our schedule of WDF, WDM, debugging and other seminars visit:
> >> http://www.osr.com/seminars
> >>
> >> To unsubscribe, visit the List Server section of OSR Online at
> >> http://www.osronline.com/page.cfm?name=ListServer
> >>
> >>
> >
> >
> > –
> > Helder Daniel
> > UALG - FCT
> > DEEI
> >
> > http://w3.ualg.pt/~hdaniel
> >
> > —
> > NTDEV is sponsored by OSR
> >
> > OSR is HIRING!! See http://www.osr.com/careers
> >
> > For our schedule of WDF, WDM, debugging and other seminars visit:
> > http://www.osr.com/seminars
> >
> > To unsubscribe, visit the List Server section of OSR Online at
> > http://www.osronline.com/page.cfm?name=ListServer
>
>
>
> —
> NTDEV is sponsored by OSR
>
> OSR is HIRING!! See http://www.osr.com/careers
>
> For our schedule of WDF, WDM, debugging and other seminars visit:
> http://www.osr.com/seminars
>
> To unsubscribe, visit the List Server section of OSR Online at
> http://www.osronline.com/page.cfm?name=ListServer
>
>


Helder Daniel
UALG - FCT
DEEI

http://w3.ualg.pt/~hdaniel</http:>

Ok I see your point.
RTC isn’t issuing interrupts while timer is

On 26 May 2013 02:59, wrote:

> > If I ran cat /proc/interrupts it just shows IRQ0 line in use by timer
> and 8 by rtc1 (it does not
> >metion rtc_cmos module):
>
> What about the second column in a table? Does not it suggest anything to
> you???
>
> Anton Bassov
>
> —
> NTDEV is sponsored by OSR
>
> OSR is HIRING!! See http://www.osr.com/careers
>
> For our schedule of WDF, WDM, debugging and other seminars visit:
> http://www.osr.com/seminars
>
> To unsubscribe, visit the List Server section of OSR Online at
> http://www.osronline.com/page.cfm?name=ListServer
>
>


Helder Daniel
UALG - FCT
DEEI

http://w3.ualg.pt/~hdaniel

Hi Don,

Thanks for the info and the link.
I’ll give it a try.

On 25 May 2013 21:20, Don Burn wrote:

> In general if the OS has grabbed a resource you can’t use it. Joe was
> referring to an old device simulator that he and Ed Dekker did, you can
> find the sources at
> http://www.eclectic-eng.com/ downloadableFiles/ SimulatorAndDriver.ziphttp: This may or may not work, but at least would be a possible starting
> point. Your code is a user space program, which is not going to be able to
> handle an INT instruction like that.
>
>
>
> Don Burn
> Windows Filesystem and Driver Consulting
> Website: http://www.windrvr.com
> Blog: http://msmvps.com/blogs/**WinDrvr http:
>
>
>
> “Helder Daniel” wrote in message news:xxxxx@ntdev:
>
> Hi newcomer,
>>
>> Thank four your suggestion.
>>
>> I tried that too as an alternative. I tried in a user space program to
>> issue an int mnemonic (I am using Windows 8 64 bits):
>>
>> int _tmain(int argc, _TCHAR* argv) {
>> _asm { int 0x8 }
>> }
>>
>> But even running it as administrator It gives me an exception:
>>
>> Unhandled exception at 0x00B514D5 in issueInt.exe: 0xC0000005: Access
>> violation reading location 0xFFFFFFFF.
>>
>> I tried the instruction int with other arguments than 8. Tried with free
>> IRQ lines (checked on device manager some free IRQ lines) but it gives me
>> the same exception.
>>
>> I am not sure if the argument of int is the IRQ line, maybe its the entry
>> in the IDT?
>> I tried with some other values but still have the exception.
>> Can you tell me what argument you used in your program?
>>
>> On the other hand maybe the system prevents issue soft interrupts from
>> user
>> space. (The syscalls now are not called using int but SYSENTER
>> mnemonic…)?
>>
>> If I tried to do that in a kernel mode driver compiler won’t let me
>> compile
>> it, giving error:
>>
>> error C4235: nonstandard extension used : ‘_asm’ keyword not supported on
>> this architecture
>>
>>
>>
>> On 25 May 2013 17:34, wrote:
>>
>> > Some years ago, we did a device simulator. We had a process that called
>> > int n, where n was the desired interrupt. It worked just fine as long
>> as
>> > you had the multiprocessor HAL installed. These days, I don’t know of
>> any
>> > machine that has the uniprocessor HAL. So just write a program that
>> > issues an int n instruction for whatever n you want, and run it. There
>> is
>> > no need to replace an existing driver to do this.
>> > joe
>> >
>> > > Hi Don,
>> > >
>> > > Thanks for the quick reply.
>> > >
>> > > I Thought RTC driver was only required at boot to update system time
>> and
>> > > at
>> > > shutdown to update RTC with current system time.
>> > > So I assumed that there is no problem removing the driver while
>> system is
>> > > running.
>> > >
>> > > I did the same thing with Linux without problems.
>> > > I removed rtc_cmos module, the Linux RTC driver, while system is
>> running
>> > > without (at least) visible side effects.
>> > >
>> > > Then I installed a demo driver which implements an IRQ8 ISR.
>> > > The driver is fully functional.
>> > >
>> > > This demo program is just for students get used with simple ISR
>> > > implementation.
>> > > I used RTC in Linux with fair success. Students can test the ISR on
>> any
>> > > computer without the need of additional boards.
>> > >
>> > > Now I want to exemplify ISR handling with Windows too.
>> > > The porting of the Linux Version for Windows is very straightforward.
>> The
>> > > only problem is that I need some device to issue interrupts. If not
>> the
>> > > RTC
>> > > I can use another one, but I would like to use a common device,
>> present
>> > in
>> > > any computer, so that students do not need to get additional hardware.
>> > >
>> > >
>> > >
>> > >
>> > >
>> > > On 25 May 2013 13:49, Don Burn wrote:
>> > >
>> > >> This is a really bad idea. If you need something for demo purposes
>> get
>> > >> a
>> > >> demo board, but messing with the real time clock will break Windows.
>> > >>
>> > >>
>> > >> Don Burn
>> > >> Windows Filesystem and Driver Consulting
>> > >> Website: http://www.windrvr.com
>> > >> Blog: http://msmvps.com/blogs/****WinDrvrhttp:
>> > >> http:
>> >
>> > >>
>> > >>
>> > >>
>> > >> “xxxxx@ualg.pt” wrote in message
>> news:xxxxx@ntdev:
>> > >>
>> > >>
>> > >> Hi all,
>> > >>>
>> > >>> I am developing a driver to implement an ISR for demo purposes.
>> > >>> I am planning to use IRQ 8 and the RTC to generate periodic
>> interrupts.
>> > >>>
>> > >>> So I need to find a way to prevent system driver cmos/rtc to load
>> at
>> > >>> boot in windows 8,
>> > >>> since with the driver loaded I can not access resources reserved by
>> it,
>> > >>> like IRQ line 8 ant I/O ports 0x70-71, which I need for my driver.
>> > >>>
>> > >>> The problem is:
>> > >>> Windows 8 at boot loads a system driver that reserves this IRQ and
>> can
>> > >>> not be disabled.
>> > >>> On the other hand if uninstalled it requires a reboot to complete
>> the
>> > >>> uninstall process but at the next boot the driver is loaded again
>> :-(.
>> > >>>
>> > >>> I tried to avoid this driver to load at boot commenting lines that
>> > >>> refers
>> > >>> to it (device id is *PNP0B00) at c:\Windows\Inf\machine.inf
>> > >>>
>> > >>> ;%*PNP0B00.DeviceDesc% = NO_DRV_X, *PNP0B00 ; Real Time
>> Clock
>> > >>>
>> > >>> ;*pnp0b00.DeviceDesc=“System CMOS/real time clock”
>> > >>>
>> > >>> and then regenerate machine.pnf, but the driver still loads.
>> > >>>
>> > >>> Then I also commented on machine.inf_loc:
>> > >>>
>> > >>> ;*pnp0b00.DeviceDesc=“System CMOS/real time clock”
>> > >>>
>> > >>> but the driver still loads :-(.
>> > >>>
>> > >>> I also found another instances of these files on other dirs and
>> > >>> commented
>> > >>> it, but with no luck.
>> > >>>
>> > >>> I thought that machine.inf specifies the drivers to load at boot
>> but it
>> > >>> seams that do not.
>> > >>> Can anyone tell me what am I missing?
>> > >>>
>> > >>> There is another way to prevent a system driver like cmos/rtc to
>> load
>> > >>> at
>> > >>> boot?
>> > >>>
>> > >>> I would appreciate any suggestions on this issue.
>> > >>> Thanks
>> > >>>
>> > >>
>> > >>
>> > >> —
>> > >> NTDEV is sponsored by OSR
>> > >>
>> > >> OSR is HIRING!! See http://www.osr.com/careers
>> > >>
>> > >> For our schedule of WDF, WDM, debugging and other seminars visit:
>> > >> http://www.osr.com/seminars
>> > >>
>> > >> To unsubscribe, visit the List Server section of OSR Online at
>> > >> http://www.osronline.com/page. **cfm?name=ListServerhttp:
>> <
>> > http://www.osronline.com/page.
cfm?name=ListServerhttp:
>> >
>> > >>
>> > >>
>> > >
>> > >
>> > > –
>> > > Helder Daniel
>> > > UALG - FCT
>> > > DEEI
>> > >
>> > > http://w3.ualg.pt/~hdaniel
>> > >
>> > > —
>> > > NTDEV is sponsored by OSR
>> > >
>> > > OSR is HIRING!! See http://www.osr.com/careers
>> > >
>> > > For our schedule of WDF, WDM, debugging and other seminars visit:
>> > > http://www.osr.com/seminars
>> > >
>> > > To unsubscribe, visit the List Server section of OSR Online at
>> > > http://www.osronline.com/page. cfm?name=ListServerhttp:
>> >
>> >
>> >
>> > —
>> > NTDEV is sponsored by OSR
>> >
>> > OSR is HIRING!! See http://www.osr.com/careers
>> >
>> > For our schedule of WDF, WDM, debugging and other seminars visit:
>> > http://www.osr.com/seminars
>> >
>> > To unsubscribe, visit the List Server section of OSR Online at
>> > http://www.osronline.com/page.
cfm?name=ListServerhttp:
>> >
>> >
>>
>>
>> –
>> Helder Daniel
>> UALG - FCT
>> DEEI
>>
>> http://w3.ualg.pt/~hdaniel
>>
>
>
> —
> NTDEV is sponsored by OSR
>
> OSR is HIRING!! See http://www.osr.com/careers
>
> For our schedule of WDF, WDM, debugging and other seminars visit:
> http://www.osr.com/seminars
>
> To unsubscribe, visit the List Server section of OSR Online at
> http://www.osronline.com/page.**cfm?name=ListServerhttp:
>
>


Helder Daniel
UALG - FCT
DEEI

http://w3.ualg.pt/~hdaniel</http:></http:></http:></http:></http:></http:></http:></http:></http:>