Re: File operations on a Windows Driver (character device)

On May 27 17:56, Alessio Faina wrote: > Thanks Mark and Corinna. > I'm sorry for the > and > ., > I wont make those mistakes in the future, I promise. > > Returning on the issue, I've decided to open the device with th

Re: File operations on a Windows Driver (character device)

On 05/27/2015 09:56 AM, Alessio Faina wrote: > Thanks Mark and Corinna. > I'm sorry for the > and > ., > I wont make those mistakes in the future, I promise. And yet, you did... > 2015-05-27 14:09 GMT+02:00 Corinna Vi

Re: File operations on a Windows Driver (character device)

Thanks Mark and Corinna. I'm sorry for the and ., I wont make those mistakes in the future, I promise. Returning on the issue, I've decided to open the device with the open() provided by Cygwin and then intercept the I

Re: File operations on a Windows Driver (character device)

On May 18 17:33, Alessio Faina wrote: > Ok thanks, I've been able to find the character device under > "/proc/sys/DosDevices/Global/deviceName"; now I'm stuck with the mmap > implementation; when I do mmap in the userland program it returns me > errno 19 (#define ENODEV 19 /* No such device *

Re: File operations on a Windows Driver (character device)

Alessio Faina writes: > I've got the kernelspace part on github ( > https://github.com/PicMelter/uniioShd.git ). > It consists of sys (the kernel module), testExe (loads/unloads on the > fly the module > in the kernel) and secondExe that just interact with the first > executable and the kernel > mo

Re: File operations on a Windows Driver (character device)

Yes.it's really a little world :) I've got the kernelspace part on github ( https://github.com/PicMelter/uniioShd.git ). It consists of sys (the kernel module), testExe (loads/unloads on the fly the module in the kernel) and secondExe that just interact with the first executable and the kernel

Re: File operations on a Windows Driver (character device)

Alessio Faina writes: > Well.I wrote and answered myself the question you pointed out that > is residing on stackoverflow Oh, small world :) > It was my first option I thought of to pass the pointer to the virtual > address to the userland application but > I've been asked to mantain the

Re: File operations on a Windows Driver (character device)

Well.I wrote and answered myself the question you pointed out that is residing on stackoverflow It was my first option I thought of to pass the pointer to the virtual address to the userland application but I've been asked to mantain the architecture using open(), ioctl(), mmap() etc so

Re: File operations on a Windows Driver (character device)

Alessio Faina writes: > Ok thanks, I've been able to find the character device under > "/proc/sys/DosDevices/Global/deviceName"; now I'm stuck with the mmap > implementation; when I do mmap in the userland program it returns me > errno 19 (#define ENODEV 19 /* No such device */) obviously bec

Re: File operations on a Windows Driver (character device)

Ok thanks, I've been able to find the character device under "/proc/sys/DosDevices/Global/deviceName"; now I'm stuck with the mmap implementation; when I do mmap in the userland program it returns me errno 19 (#define ENODEV 19 /* No such device */) obviously because I haven't set anything in

Re: File operations on a Windows Driver (character device)

On 05/18/2015 05:42 AM, Alessio Faina wrote: Hello everyone, I'm developing a port of a FreeBSD/Linux application that consists of two parts: a kernel and a user land part. The kernel part is build as a WDM driver and is compiled with VS2013 and WDK 8.1: the userspace is going to be compiled und