Prev: kernel base address
Next: Sony Cyber-shot DSC-W380 Digital Camera
From: Zbynek on 4 Mar 2010 12:17
So building by WDK is - how to say - we have interesting result :-P
I rebuild driver by WDK without errors and warnings - but when I try to start
this driver, system freezes (without BSOD etc.).
I test it on Win 7 prof. 64bit (update). Compile by WDK 700... (new) on the
same
system (and try by WDK 600... on XP 32bit with target platform Vista 64bit
too).
I try to find out why it's crashing - and comment all except of DriverEntry
(there are only assign service rutines and create the driver object) - but I
got
unstable result - so for one of five tryings it's OK (start/stop, nothing
more),
other freeze.

I think it of course will be better compile it by WDK's build, but now I
must it
repair fast (and later play with it).

Is it possible there is something new in commands/callings/demands from
system
to filesystem in 64bit OSs? It's going well on 32bit Win2000-Win7 but wrong
on
64bit Vista&Seven. I'm trying to debug it now but it looks well in driver -
only
access to disk from user mode is bad :-D
It looks like there is some new/obligatory calling (there are some unknow
callings from system to driver in debug log - but this calling are in 32bit
systems too and it works).
Or there is a site/list/help with what all must the driver accept/implement
for
good working?

Thanks very much
Zbynek
(developer of Cosect s.r.o)
From: eagersh on 5 Mar 2010 13:06
On Mar 4, 10:17 am, Zbynek <Zby...(a)discussions.microsoft.com> wrote:

> Is it possible there is something new in commands/callings/demands from
> system
> to filesystem in 64bit OSs?
Not likely.

>It's going well on 32bit Win2000-Win7 but wrong
> on
> 64bit Vista&Seven. I'm trying to debug it now but it looks well in driver -
> only
> access to disk from user mode is bad :-D
Could you give more details what is wrong?


> Or there is a site/list/help with what all must the driver accept/implement
> for
> good working?
Where is your driver set up? Is it a filter of Disk Class?

Igor Sharovar
From: Zbynek on 9 Mar 2010 14:19
"eagersh" wrote:

> Could you give more details what is wrong?
>
> Where is your driver set up? Is it a filter of Disk Class?
>
> Igor Sharovar

So, I was testing driver for last week :-)
To your questions - this driver is filter driver (system sends request to
this driver and this driver send I/O request to low level drivers - ntfs/fat).

I install it now by myself (start/stop), but in full version it will be
install by inf file and running all time (start when user log in and stop
when log out).

So, actual review is:
- driver is running, drives are connected to system (we can see a drive
letter, driver cans open this drive, system sends request to this drive
through)

- this week, first I thought the error was in bad structure (on 64bit)
which was returned on request for drive size / drive geometry etc. But I
tested it again and think that it works...
But if there is any good practise how to test it well, I will be glad :-)
Becouse the system's review of attached disk (propertis in explorer etc.)
shows zero length (and zero alls propertis). But system sends requests for
this properties and driver return non zero values... (in structures which are
running on 32bit and moustly are from system libraries).

- now I'm debbuging the read requests - systems send them, but only several
times for first 512bytes from the disk spaces (on ntfs file system) - and
then tell to the user that there is an error (in console unknow filesystem or
bad drive/driver). The begining of the drive is correct (this drive is
running correctly with 32bit system where was created).

So I will debug what driver get back from filesystem a what get back system
when it sends this request.

Thank you
Zbynek
(developer of Cosect s.r.o)
 | 
Pages: 1
Prev: kernel base address
Next: Sony Cyber-shot DSC-W380 Digital Camera