Just out of Curiosity

Index > Windows > Just out of Curiosity

Author

Thread

typedef

Joined: 25 Jul 2010
Posts: 2909
Location: 0x77760000

typedef 11 Aug 2010, 04:33

As the subject suggests, is FASM able to produce Nt Drivers (.sys files) ?.

And is it possible to create a struct in 16-bit?

11 Aug 2010, 04:33

Tyler

Joined: 19 Nov 2009
Posts: 1216
Location: NC, USA

Tyler 11 Aug 2010, 05:10

> And is it possible to create a struct in 16-bit?
The struc is a specialized Fasm macro, independent of bitness. So yes.

> s the subject suggests, is FASM able to produce Nt Drivers (.sys files) ?.
Yes. I think. I've never tried it, but the docs say it does. http://flatassembler.net/docs.php?article=manual#2.4.2

11 Aug 2010, 05:10

typedef

Joined: 25 Jul 2010
Posts: 2909
Location: 0x77760000

typedef 11 Aug 2010, 05:44

Ok. another question, in the following drive table where would a flash disk be. On my PC (its G: for USB thumbs and E: for PSP ) so how would i know which is which

Code:

Drive Table
DL = 00h   1st floppy disk ( "drive A:" )
DL = 01h        2nd floppy disk ( "drive B:" )
DL = 80h        1st hard disk
DL = 81h       2nd hard disk

11 Aug 2010, 05:44

Tyler

Joined: 19 Nov 2009
Posts: 1216
Location: NC, USA

Tyler 11 Aug 2010, 06:17

I would guess it would be the second hdd.

On what level are you trying to do this? If you're trying to make a driver for USB, have fun with that. I'm sure there's some way to get info for Volumes, that's if there's already a driver and you're trying to access the device as a volume(something with a drive letter).

11 Aug 2010, 06:17

vid
Verbosity in development

Joined: 05 Sep 2003
Posts: 7105
Location: Slovakia

vid 11 Aug 2010, 10:01

typedef:

FASM can't produce old VxD drivers (it used some LE/Linear executable format IIRC), but it can produce newer WDM drivers, which are just plain PE executables with extra flag set.

However, what you are posting looks like BIOS. In Windows driver, you don't use BIOS, you use MS-specific APIs to interface with hardware.

11 Aug 2010, 10:01

typedef

Joined: 25 Jul 2010
Posts: 2909
Location: 0x77760000

typedef 12 Aug 2010, 01:23

Tyler wrote:

I would guess it would be the second hdd.

On what level are you trying to do this? If you're trying to make a driver for USB, have fun with that. I'm sure there's some way to get info for Volumes, that's if there's already a driver and you're trying to access the device as a volume(something with a drive letter).

Sorry for the confusion. The second question has nothing to do with the first one. The second one i just wanted to find out how the BIOS drive table is laid out. For example if i wanted to get drive (F:\) params. How would i know the given 'ID' is Flash drive.

Code:


MOV DL,00h       ;1st floppy disk ( "drive A:\" )

      ;What would be the ID for Flash disk (F:\)?

NOTE :
This has nothing to do with making USB drivers. Im not doing that, like i said the subject says it all.

No pressure

12 Aug 2010, 01:23

Tyler

Joined: 19 Nov 2009
Posts: 1216
Location: NC, USA

Tyler 12 Aug 2010, 05:42

You probably can't. Flash drives would be emulated as external HDDs(That's what my BIOS settings calls anything usb.). So I guess 81h.

Windows and BIOS don't mix. The BIOS drive # will mean nothing to Windows. If you want info on a drive, having a BIOS id will only help you if you're working with the BIOS to get the info.

12 Aug 2010, 05:42

< Last Thread | Next Thread >

Forum Rules:

You cannot post new topics in this forum
You cannot reply to topics in this forum
You cannot edit your posts in this forum
You cannot delete your posts in this forum
You cannot vote in polls in this forum
You cannot attach files in this forum
You can download files in this forum