From - Tue Sep 16 14:12:42 1997
Path: news.mitre.org!blanket.mitre.org!news.tufts.edu!cam-news-feed5.bbnplanet.com!cam-news-hub1.bbnplanet.com!cpk-news-hub1.bbnplanet.com!news.bbnplanet.com!newsfeed.internetmci.com!192.220.251.22!netnews.nwnet.net!news.microsoft.com!news
From: "Paul Sanders" <paulsan@microsoft.com>
Newsgroups: comp.os.ms-windows.programmer.nt.kernel-mode
Subject: Re: Question: load and use SCSICDRM.SYS??
Date: 16 Sep 1997 16:14:44 GMT
Organization: Microsoft
Lines: 113
Message-ID: <01bcc2bb$3d3bbf90$8fa8369d@paulsan90>
References: <EGK8qD.L4I@mv.mv.com> <341E27F3.E5C51583@us.ibm.com>
NNTP-Posting-Host: 157.54.168.143
X-Newsreader: Microsoft Internet News 4.70.1157

I seem to recall that the SOURCES file for the 4.0 DDK are not setup to
work with the new format for the class drivers.  By new format I mean that
class.lib is now a DLL instead of a staticly linked library.

Here is the source code to three version of SOURCES.




******** CLASS2.LIB (the DLL version)

!IF 0

Copyright (c) 1989  Microsoft Corporation

!ENDIF

TARGETNAME=class2
TARGETPATH=$(BASEDIR)\lib
TARGETTYPE=EXPORT_DRIVER

TARGETLIBS=$(BASEDIR)\lib\*\$(DDKBUILDENV)\scsiport.lib

INCLUDES=..\..\inc

SOURCES=class.c \
        class.rc

DLLDEF=obj\*\class.def

NTTARGETFILE0=$(DLLDEF)


******** DISK.SYS

TARGETNAME=disk
TARGETPATH=$(BASEDIR)\lib
TARGETTYPE=DRIVER

TARGETLIBS=$(BASEDIR)\lib\*\$(DDKBUILDENV)\class2.lib        \
           $(BASEDIR)\lib\*\$(DDKBUILDENV)\scsiport.lib

INCLUDES=..\..\inc

SOURCES=disk.c          \
        scsidisk.rc



******** CDROM.SYS

TARGETNAME=cdrom
TARGETPATH=$(BASEDIR)\lib
TARGETTYPE=DRIVER

TARGETLIBS=$(BASEDIR)\lib\*\$(DDKBUILDENV)\class2.lib        \
           $(BASEDIR)\lib\*\$(DDKBUILDENV)\scsiport.lib

INCLUDES=..\..\inc

SOURCES=cdrom.c         \
        findscsi.c      \
        scsicdrm.rc


Good luck,
-Paul

Bob Crowley <greenbay@us.ibm.com> wrote in article
<341E27F3.E5C51583@us.ibm.com>...
> Assuming that you are building this from the NT DDK, you can replace
CDROM.SYS
> with the ScsiCDRM.SYS that you have built. However, I've build the CDROM
class
> driver included with the DDK and it doesn't work for me, I get a BSoD. I
have
> build the SCSI Tape class and have gotten that to work for me. I don't
think
> that the CDROM class driver provided in the DDK works on NT 4.0.
> 
> Bob
> 
> Patrick Klos wrote:
> 
> > I am trying to modify CDROM.C to accept WORM devices as well as
standard
> > CDROMs (so my WORM device will look like a CDROM to NT [what a
concept!]).
> > I can build it fine, I get SCSICDRM.SYS, but how do I install this
driver
> > since there is no equivalent driver in the system32/drivers directory? 
Is
> > this file (SCSICDRM.SYS) supposed to replace CDROM.SYS??
> >
> > Alternatively, does anyone know how I can get NT to see my WORM drive
as
> > a standard CDROM drive?  It works fine in DOS and WFW3.11!  Why
shouldn't
> > NT be able to do the same (what was Microsoft thinking?!?)?
> >
============================================================================

> >     Patrick Klos                           Email: patrick@klos.com
> >     Klos Technologies, Inc.                Voice: (603) 424-8300
> >     604 Daniel Webster Highway             FAX:   (603) 424-9300
> >     Merrimack, New Hampshire  03054        Web:   http://www.klos.com/
> >
============================================================================

> 
> 
> 
> 
