Comparing functions

[Razor]

Its a driver for 0 ring access for application,it offers what a hardware driver does... .


I want to use the old functions above in new driver...

[Mackhack]

Ok, sounds interesting but I believe the smart guys here that unknowingly tempting with that stuff can cause blue screens and therefore I let those guys mess around with that kind of technology! But keep on going man!!! More power to you!

[Razor]

It can couse it yea but if you know how to use it like Muetze1 he knows the stuff like he's here forever.


The finished project will be amd64 x2 Core temp reading with a faster driver and maybe later core 2 duo and quad...

[Mackhack]

I know Muetze1,

that's why I said before, I let those people work with hardware close apps and drivers since they know what they are doing in this field...

But again,... More power to you and your learning experience!

[Razor]

Mackhack if it will work on my system it will also work on yours it wont couse bluescreens on yours and not on mine it just not the way it goes...

[Mackhack]

You need to read again what I said... I'm not making your project bad nor am I trying to bring you down... I like when people go the trial and error way and learn something!

So stop feeling offended by me! It's all good that's why I was asking what's all about this project!

[Razor]

Okay no hard feelings

[Mackhack]

Zitat von Razor:

Okay no hard feelings

Now we're talking

[devidespe]

Zitat von Razor:

So why is it there var pdata:cardinal and in the omcdrv.pas its var pdata:dword; dont really really get it; and plus why cant i call that function.... :shock:

Just had a look at your unit.

It seems that Delphi in general (e.g. my Delphi 2007 Pro as well as your version 7) doesn't always update the function parameters for the internal programmer help, which is displayed after entering k.IPCIIORef.

You can be sure that GetPCIRDWord doesn't contain a cardinal value, just a DWord value. If you are confused by the hint of the programmer help, use a DWord variable, compile it and have a look at the bottom messages list. Would the function really need a cardinal variable, there should be a message entry.

Had the same problem here too and Delphi needs sometimes a complete code compilation (sometimes 2 or 3 times) to know, that a variable is a DWord and not a Cardinal. But that must have mean, that a cardinal type was there previously.

To be sure just search the entire unit after a cardinal value - you won't find some. That is the acnowledgement that there isn't one. Hope that helps...

[Razor]

As you can see here i was experimenting something and the below looked like is it gonna happen but should i worry about warning?

Delphi-Quellcode:

procedure tmainfrm.amd64x2start;
var
C0:string;
GetInstance:tomcdrv;
pdata: DWord;
begin

       GetInstance.IPCIIORef.GetPCIRDWord(0,24,$03,$E4,pdata);
       GetInstance.IPCIIORef.SetPCIRDWord(0,24,$03,$E4, pdata and not (1 shl 2));
       GetInstance.IPCIIORef.GetPCIRDWord(0,24,$03,$E4,pdata);
       C0:=Format('%d °C',[(pdata shr 16 and $FF)-49]);
       RzLabel99.caption:=C0;

//But then i get [Warning] Temperatures.inc(117): Variable 'GetInstance' might not have been initialized

Or.....

Delphi-Quellcode:

procedure tmainfrm.amd64x2start;
var
C0:string;

pdata: DWord;
begin

       OMCDRV.tGetPCIRDWord(0,24,$03,$E4,pdata);
       OMCDRV.tSetPCIRDWord(0,24,$03,$E4, pdata and not (1 shl 2));
       OMCDRV.tGetPCIRDWord(0,24,$03,$E4,pdata);
       C0:=Format('%d °C',[(pdata shr 16 and $FF)-49]);
       RzLabel99.caption:=C0;

//But then i get [Fatal Error]Internal error: BA1993 or [Fatal Error] Internal error: L1333