LLXX Posted November 14, 2006 Share Posted November 14, 2006 I meant the version number, e.g. 4.10.2222 Link to comment Share on other sites More sharing options...
Petr Posted November 14, 2006 Share Posted November 14, 2006 I meant the version number, e.g. 4.10.2222So I gave you the answer, or do you need any additional information?Petr Link to comment Share on other sites More sharing options...
LLXX Posted November 15, 2006 Share Posted November 15, 2006 I meant the version number, e.g. 4.10.2222So I gave you the answer, or do you need any additional information?PetrI was asking what version number of the files are the symbols for! Link to comment Share on other sites More sharing options...
Petr Posted November 15, 2006 Share Posted November 15, 2006 (edited) I meant the version number, e.g. 4.10.2222So I gave you the answer, or do you need any additional information?PetrI was asking what version number of the files are the symbols for! I don't know how to get this information from those .SYM files but what version would you expect in symbols for first and Second Edition? I'd suppose that the versions are 4.10.1998 and 4.10.2222 respectively.PetrEdit: I have reviewed the contents again and:WIN98DDK\DEBUG_WINDOWS98SE\RETAIL fontains just .SYM files with no information about the file version but as MS declare that it is for Windows 98 SE so why not to believe them?c:\TEMP\WIN98DDK\DEBUG_WINDOWS98SE\DEBUG contains bot .SYS and binary files and the versions are: 4.10.0.2222 1394BUS.SYS 4.10.0.2222 ACPI.SYS 4.80.0.1675 ADVAPI32.DLL 4.10.0.2222 BATTC.SYS 4.10.0.2222 CBSS.VXD 4.10.0.2222 CCPORT.SYS 4.10.0.2222 CDVSD.VXD 4.10.0.2222 CMBATT.SYS 4.10.0.2222 COMPBATT.SYS 4.10.0.2222 CONFIGMG.VXD 4.6.3.518 DINPUT.VXD 4.10.0.2222 DISKTSD.VXD 4.10.0.2222 ESDI_506.PDR 4.10.0.2222 GDI.EXE 4.10.0.1998 GDI32.DLL 4.10.0.2222 HID.DLL 4.10.0.2222 HIDCLASS.SYS 4.10.0.2222 HIDPARSE.SYS 4.10.0.2222 HIDUSB.SYS 4.10.0.2222 IFSMGR.VXD 4.10.0.2222 IOS.VXD 4.10.0.2222 IRENUM.VXD 4.10.0.2222 JOYHID.VXD 4.10.0.2222 KBDHID.VXD 4.10.0.2222 KERNEL32.DLL 4.10.0.2222 KMIXER.SYS 4.10.0.1998 KRNL386.EXE 4.10.0.2222 KS.SYS 4.10.0.2222 KSCLOCKF.AX 4.10.0.2222 KSDATA.AX 4.10.0.2222 KSINTERF.AX 4.10.0.2222 KSPROXY.AX 4.10.0.2222 KSVPINTF.AX 4.3.0.2200 MMCI.DLL 4.10.0.2222 MOUHID.VXD 4.10.0.2222 MSDV.SYS 4.10.0.2222 MSKSSRV.SYS 4.10.0.2222 NDIS.VXD 4.10.0.2222 NTKERN.VXD 4.10.0.2222 OHCI1394.SYS 4.10.0.2222 OPENHCI.SYS 4.10.0.2222 PCCARD.VXD 4.10.0.2222 PCI.VXD 4.10.0.2222 PORTCLS.SYS 4.10.0.2222 PPPMAC.VXD 4.10.0.2222 REMOTESP.TSP 5.0.1755.1 RSVPSP.DLL 4.10.0.2222 SCSIPORT.PDR 4.10.0.2222 SECUR32.DLL 4.10.0.2222 SERENUM.VXD 4.10.0.2222 STREAM.SYS 4.10.0.2222 SWMIDI.SYS 4.10.0.2222 SYSAUDIO.SYS 4.10.0.2222 TAPI32.DLL 4.10.0.2222 TAPISRV.EXE 4.10.0.2222 UDF.VXD 4.10.0.2222 UHCD.SYS 4.10.0.2222 UNIMODEM.VXD 4.10.0.2222 USBAUDIO.SYS 4.10.0.2222 USBD.SYS 4.10.0.2222 USBHUB.SYS 4.10.0.2222 USBSER.SYS 4.10.0.2222 USER.EXE 4.10.0.2222 USER32.DLL 4.10.0.2222 VCOMM.VXD 4.10.0.2222 VDD.VXD 4.10.0.2161 VDHCP.386 4.10.0.2222 VFWWDM.DRV 4.10.0.2222 VFWWDM32.DLL 4.10.0.2222 VIP.386 4.10.0.2222 VMM.VXD 4.10.0.2222 VMOUSE.VXD 4.10.0.2148 VNBT.386 4.10.0.2222 VPICD.VXD 4.10.0.2222 VREDIR.VXD 4.10.0.2222 VTCP.386 4.10.0.1998 VWIN32.VXD 4.10.0.2222 VXDLDR.VXD 4.10.0.2222 WAN.TSP 4.10.0.2222 WDMAUD.SYS 4.10.0.2222 WDMMDMLD.VXD 4.10.0.2222 WMIDRV.SYS 4.10.0.2222 WS2_32.DLLand this is the list of symbols in this folder:1394BUS.SYMACPI.SYMADVAPI32.SYMCBSS.SYMCCPORT.SYMCDVSD.SYMCONFIGMG.SYMDINPUT.SYMDISKTSD.SYMESDI_506.SYMGDI.SYMHID.SYMHIDCLASS.SYMHIDPARSE.SYMHIDUSB.SYMIFSMGR.SYMIOS.SYMIRENUM.SYMJOYHID.SYMKBDHID.SYMKERNEL32.SYMKMIXER.SYMKRNL386.SYMKS.SYMKSCLOCKF.SYMKSDATA.SYMKSINTERF.SYMKSPROXY.SYMKSVPINTF.SYMMMCI.SYMMOUHID.SYMMSDV.SYMMSKSSRV.SYMNDIS.SYMNTKERN.SYMOHCI1394.SYMOPENHCI.SYMPCCARD.SYMPCI.SYMPORTCLS.SYMPPPMAC.SYMREMOTESP.SYMRSVPSP.SYMSCSIPORT.SYMSECUR32.SYMSETUPX.SYMSTREAM.SYMSWMIDI.SYMSYSAUDIO.SYMTAPI32.SYMTAPISRV.SYMUDF.SYMUHCD.SYMUNIMODEM.SYMUSBAUDIO.SYMUSBD.SYMUSBHUB.SYMUSBSER.SYMUSER.SYMUSER32.SYMVCOMM.SYMVDD.SYMVDHCP.SYMVFWWDM.SYMVFWWDM32.SYMVIP.SYMVMM.SYMVMOUSE.SYMVNBT.SYMVPICD.SYMVREDIR.SYMVTCP.SYMVWIN32.SYMVXDLDR.SYMWAN.SYMWDMAUD.SYMWDMMDMLD.SYMWMIDRV.SYMDo you need any more information?Petr Edited November 15, 2006 by Petr Link to comment Share on other sites More sharing options...
LLXX Posted November 16, 2006 Share Posted November 16, 2006 In other words, the symbols would probably not work for newer versions (e.g. 4.10.2225 ESDI_506.PDR) Link to comment Share on other sites More sharing options...
tErmY Posted November 16, 2006 Share Posted November 16, 2006 MSDN Version is about 45 MB (contains also symbols) and the file name is WIN98DDK.EXE.Symbols for what version of the files?What's a symbol file? Link to comment Share on other sites More sharing options...
eidenk Posted November 16, 2006 Share Posted November 16, 2006 MSDN Version is about 45 MB (contains also symbols) and the file name is WIN98DDK.EXE.Symbols for what version of the files?What's a symbol file?I wanted to ask the same question. And also what are they used for ? And why are they available only to MSDN subscribers ? Link to comment Share on other sites More sharing options...
Petr Posted November 16, 2006 Share Posted November 16, 2006 (edited) Symbol files contain symbols for given executable, i.e. assignment between addresses and symbols for subroutines, entry points etc.Symbol files are intended to be used for debugging and can be used by some disassemblers too.There are also special builds of Windows intended for debugging with inserted code that sends information to the debugging output.You should ask Microsoft why these files are available to MSDN subscribers only - maybe they think that who else could need them?PetrIn other words, the symbols would probably not work for newer versions (e.g. 4.10.2225 ESDI_506.PDR)If offsets are different then they cannot be used directly.Sometimes I use the following procedure with Sourcer:1. Generate wdf file using e.g. 4.10.2222 dll version with symbols2. Generate wdf file using e.g. 4.10.2225 dll version without symbols3. Manually write symbols from wdf file for 4.10.2222 to wdf file for 4.10.2225. Compare listings to see what are the same procedures and entry points.Not very efficient but possible.Petr Edited November 16, 2006 by Petr Link to comment Share on other sites More sharing options...
coq Posted January 14, 2007 Share Posted January 14, 2007 (edited) Hi, if you don't want to use DDK, you can use third party softwares that let you write your driver in many compilers including C++. WinDriver is a good driver development toolkit although not free (they have a fully featured evaluation version..).You can check out( http:http://www.jungo.com/windriver.html#driver-development-usb-pci) Edited January 14, 2007 by coq Link to comment Share on other sites More sharing options...
Recommended Posts
Create an account or sign in to comment
You need to be a member in order to leave a comment
Create an account
Sign up for a new account in our community. It's easy!
Register a new accountSign in
Already have an account? Sign in here.
Sign In Now