I am trying to eliminate all compiler-warnings of a given project. I'm stuck with the warning below;
Processing COM reference "AXDBLib" from path "(somepath)axdb20enu.tlb". Interface 'IAcadShadowDisplay' is marked as [dual], but does not derive from IDispatch. It will be converted as an IUnknown-derived interface.
Ideally, I would like to understand how to rectify it, but if that is not possible, I'd like to surpress it.
I have a Win8 PC with a Win7 virtual machine (VirtualBox) where I do development because we use VS 6.0. (Yes, I know, hard to believe.) Anyway, each time I do a build, I have to delete other builds, to free up disk space. It is getting to the point where soon I will have no free disk space. It looks as if Windows Updates are expanding the OS. Is there anything I can do? Is there a folder with unwanted OS update files?
I can expand the virtual disk, from the current 80GB, but that is only a temporary fix for obvious reasons. I have to have SQL server etc on the virtual machine, which take up quite a few GB.
Friends,I am working on a project....and in that project i have to take scanned image of finger with the help of fingerprint scanner.....and this image will be used as a password to log in the site.....so plzzzz..tell me how to store images in database..and how can i check the scanned image of finger of user with other scanned images
I have found that for linux it is possible to use vga, hdmi and other video connector's ddc's i2c ports to program and communicate with periphial devices. I have also found that apparently no one has been able to do it for windows, with the exception to nicomsoft. Nicomsoft has software that I have verified can read the i2c ports and not just access edid registry. I have an accelerometer connected and when I run the software it can detect a device at it's address. So I know it is possible but I have no idea if it is possible to use windows to do it. I know windows video port driver can call the miniport driver and get pointers to i2c callback structure containing explicit controls of the clock and data lines. The problem is it does not seem to export any of these pointers to anything else, like a user api let alone another kernal mode driver. I have considered that it might be possible at a hardware level were I have found out the intrcacies of the hardware, I have even seen an example of a video miniport driver on this site. I have an amd laptop which uses the bolton fusion controller hub which has vga ddc i2c ports. If you search amd docs for bolton fch you can find the documentation. basically I know the hub's i2c ports physical pins which my guess are both strung out to the hdmi and vga port's on my lap top. I have alos looked up the hub's general pupose i/o registers and it appears that they correspond to the pins. For instance ddc_i2c_scline is gpin70 and the data gpin71. the gpio registers are numbered correspondingly except the decimal pin number is changed to hexidecimal for the register. I can find the memory offset. My question is now, can I call gdi's function to map video memory to the process virtual memory, then write to these registers, turning them on and off? It is difficult to tell just what perspective on the memory I will have. Also if this worked, it would not be platform independent and would only work for pc's with bolton fusion controller hubs. Nicomsoft's program seems to be platform independent so either it wrote drivers for all common hardwares or it is using windows video port driver somehow? I have been working on this for several months and if someone could please help it would be awsome. thanks.
I'm currently reading a computer organization book and i'm so confused about Input/Output mechanism and have lots of questions in my mind.
As i understood there are two concepts for communicating with peripherals, first one is Memory Mapped I/O and the other one is I/O(Port) Mapped I/O.If the architecture is based on Memory Mapped I/O there are no special I/O instructions like "in","out" etc and device registers are mapped to memory address space so we can read or write to peripheral ports by "mov" instruction.On the other hand if architecture is based on I/O Mapped I/O, device registers are mapped to I/O address space which is completely separated from memory address space and cpu uses special instructions("in","out","ins","outs" ) for reading or writing to I/O Mapped device registers.
So here is my questions;
1.)If X86 architecture uses I/O(Port,Isolated etc) Mapped I/O technique why there are memory address spaces for devices like graphic card?
2.)If graphic card maps 1 gb memory to main memory address space what does it mean?Does it mean Memory Mapped I/O ?
3.)If x86 architecture doesn't use Memory Mapped I/O how a device can maps itself to memory address space?
4.)If x86 architecture can use Memory Mapped I/O ,how can it use and with which instructions?
5.)If I/O mapping is about mapping peripheral registers why graphic card wants so much space for mapping ?
Ok so I've read that there are some instructions that do things that enable/disable interupts,etc
are these the so-called priviledged instructions ??
do you know if there is a list with all those "strange" instructions ?
Last Visit: 31-Dec-99 19:00 Last Update: 1-Mar-24 11:54