Full Version: <DELETED>
<deleted>
Not sure if this is what you want... but here you go: http://www.filewatcher.com/_/?q=win98ddk
It's not the most recent version.
Oops.
QUOTE (SFan00 @ Nov 8 2006, 06:27 PM) 
Hi,
been trying to track down the 98DDK which was for a while on
the MSDN site but seems to have been a casulty of the end of
Windows 9x support.
Any ideas on how to get hold of it, as it was at one point
available as a no-charge download?
been trying to track down the 98DDK which was for a while on
the MSDN site but seems to have been a casulty of the end of
Windows 9x support.
Any ideas on how to get hold of it, as it was at one point
available as a no-charge download?
Here is the explanation: http://msdn.microsoft.com/subscriptions/msjvm/
Fortunately I have everything on CD-ROMs.
And here is the latest Windows 98 DDK: http://www.arte.unipi.it/Public/Win32/win98ddk.exe
Petr
Nice link Petr. I also found there the Windows ME Debugger Kit. Something I ignored existed until now.
http://www.arte.unipi.it/Public/Win32/winmekdb.exe
http://www.arte.unipi.it/Public/Win32/winmekdb.exe
The original filename is "98DDK.EXE" and it is approximately 25Mb. If you do some Searching on the internet you will definitely find it.
It used to be at http://download.microsoft.com/download/win...EN-US/98DDK.EXE but I suppose M$ removed it immediately after the end of 9x support.
It used to be at http://download.microsoft.com/download/win...EN-US/98DDK.EXE but I suppose M$ removed it immediately after the end of 9x support.
QUOTE (LLXX @ Nov 9 2006, 03:45 AM)
The original filename is "98DDK.EXE" and it is approximately 25Mb. If you do some Searching on the internet you will definitely find it.
MSDN Version is about 45 MB (contains also symbols) and the file name is WIN98DDK.EXE.
Petr
is the windows me driver kit the same as the windows 98 driver kit?
QUOTE (StateS @ Nov 13 2006, 12:11 AM)
is the windows me driver kit the same as the windows 98 driver kit?
I have never seen it so probably yes.
Petr
there is a sperate DDK for ME.
QUOTE (MagicAndre1981 @ Nov 13 2006, 12:18 PM)
there is a sperate DDK for ME.
Interesting. I have the following CDs and DVDs from MSDN:
1009 (Nov 2001) contains:
Windows 98 DDK,
Windows 2000 Driver Development Kit - October 2000 Edition,
Windows XP Driver Development Kit
1009.1 (Feb 2003) contains:
Windows 98 DDK,
Windows 2000 Driver Development Kit - October 2000 Edition,
Windows XP Service Pack 1 Driver Development Kit
1009.2 (May 2003) contains:
Windows XP Driver Development Kit,
Windows Server 2003 Driver Dvelopment Kit
1797 (Oct 2002) contains
Windows .NET Server Release Candidate 1 Driver Development Kit
1968 (Feb 2003) contains:
Windows 98 DDK,
Windows 2000 DDK - October 2000 Edition,
Windows XP SP1 DDK
2426.15 (Jul 2005) contains:
Windows XP SP1 DDK,
Windows Server 2003 with SP1 DDK
There was also nothing in Subscribers download section.
But I see a note in Q322361:
QUOTE
To obtain Windows Me DDK content, download the Microsoft Windows 2000 DDK
Petr
you wrote the answer 
There is a DDK of Win2k with an integrated WinME-DDK
There is a DDK of Win2k with an integrated WinME-DDK
QUOTE (Petr @ Nov 9 2006, 02:33 AM)
MSDN Version is about 45 MB (contains also symbols) and the file name is WIN98DDK.EXE.
Symbols for what version of the files?
QUOTE (LLXX @ Nov 14 2006, 02:16 AM)
QUOTE (Petr @ Nov 9 2006, 02:33 AM)
MSDN Version is about 45 MB (contains also symbols) and the file name is WIN98DDK.EXE.
Symbols for what version of the files?Both FE and SE, both debug and retail versions.
CODE
Windows 98 Debug Binaries and Symbols
-------------------------------------
The Windows 98 DDK ships with a number of debug versions of core
Windows 98 system components and drivers. These binaries are intended
to aid in testing and debugging drivers developed with the Windows 98
DDK.
Below is a list of the binaries currently shipped with the Windows 98
DDK, and the directory each binary needs to be copied to for it to be
loaded by Windows 98. The debug symbol files are also included, they
have the same base name ending with the extension .SYM. Please refer
to the documentation for the WDEB98 system debugger for information on
how to use the specific debugging features of each debug binary.
NOTE: There is a version dependence between VWIN32.VXD, KERNEL32.DLL,
and KRNL386.EXE. You must run with either all retail versions of
these binaries or all debug versions. Mixing retail and debug
versions of these binaries will result in Windows 98 hanging or
faulting during boot.
System VxDs
-----------
VMM.VXD \windows\system\vmm32
VWIN32.VXD \windows\system\vmm32
VPICD.VXD \windows\system\vmm32
VXDLDR.VXD \windows\system\vmm32
VDMAD.VXD \windows\system\vmm32
DEBUGCMD.VXD \windows\system (loaded statically via system.ini entry)
System DLLs
-----------
GDI.EXE \windows\system
KRNL386.EXE \windows\system
USER.EXE \windows\system
GDI32.DLL \windows\system
KERNEL32.DLL \windows\system
MAPI32.DLL \windows\system
USER32.DLL \windows\system
SETUPX.DLL \windows\system
WDM
---
NTKERN.VXD \windows\system\vmm32
WMIDRV.SYS \windows\system32\drivers
PnP
---
CONFIGMG.VXD \windows\system\vmm32
PCI.VXD \windows\system
ISAPNP.VXD \windows\system
BIOS.VXD \windows\system
EISA.VXD \windows\system
1394
----
1394BUS.SYS \windows\system32\drivers
TILYNX.SYS \windows\system32\drivers
OHCI1394.SYS \windows\system32\drivers
AHA899X.SYS \windows\system32\drivers
WDM Streaming (WDM Audio, Video Capture, DVD, etc.)
---------------------------------------------------
STREAM.SYS \windows\system32\drivers
KSCLOCKF.AX \windows\system
KSDATA.AX \windows\system
KSINTERF.AX \windows\system
KSPROXY.AX \windows\system
KSYPINTF.AX \windows\system
KS.SYS \windows\system32\drivers
MSKSSRV.SYS \windows\system32\drivers
KSUSER.DLL \windows\system
USB
---
OPENHCI.SYS \windows\system32\drivers
UHCD.SYS \windows\system32\drivers
USBD.SYS \windows\system32\drivers
USBDIAG.SYS \windows\system32\drivers
USBHUB.SYS \windows\system32\drivers
OnNow/ACPI
----------
ACPI.SYS \windows\system
BATTC.SYS \windows\system
CMBATT.SYS \windows\system
COMPBATT.SYS \windows\system
EC.SYS \windows\system
Still Image
-----------
USBSCAN.SYS \windows\system32\drivers
Multimedia
----------
SYSAUDIO.SYS \windows\system32\drivers
USBAUDIO.SYS \windows\system32\drivers
WDMAUD.SYS \windows\system32\drivers
MMDEVLDR.VXD \windows\system
MMCI.DLL \windows\system
MIDIMAP.DRV \windows\system
MMSOUND.DRV \windows\system
WDMAUD.DRV \windows\system (symbol file is named wdmdrv.sym)
MMSYSTEM.DLL \windows\system
MSACM.DLL \windows\system
MSACM32.DLL \windows\system
WINMM.DLL \windows\system
Storage
-------
CDTSD.VXD \windows\system\iosubsys
CDVSD.VXD \windows\system\iosubsys
DISKTSD.VXD \windows\system\iosubsys
DISKVSD.VXD \windows\system\iosubsys
IOS.VXD \windows\system\vmm32
RMM.PDR \windows\system\iosubsys
SCSIPORT.PDR \windows\system\iosubsys
VFAT.VXD \windows\system\vmm32
CDFS.VXD \windows\system\iosubsys
VOLTRACK.VXD \windows\system\iosubsys
IFSMGR.VXD \windows\system\vmm32
HID
---
HIDCLASS.SYS \windows\system32\drivers
HIDPARSE.SYS \windows\system32\drivers
HIDUSB.SYS \windows\system32\drivers
MOUHID.VXD \windows\system
JOYHID.VXD \windows\system
KBDHID.VXD \windows\system
VKD.VXD \windows\system\vmm32
VJOYD.VXD \windows\system
HID.DLL \windows\system
MMHID.DLL \windows\system
VMOUSE.VXD \windows\system\vmm32
Display
-------
VDD.VXD \windows\system\vmm32
VFLATD.VXD \windows\system\vmm32
DIBENG.DLL \windows\system
Networking
----------
NDISWAN.VXD \windows\system
PPPMAC.VXD \windows\system
VDHCP.386 \windows\system
VIP.386 \windows\system
VNBT.386 \windows\system
VTCP.386 \windows\system
VTDI.386 \windows\system
VUDP.386 \windows\system
NDIS.VXD \windows\system
NETDI.DLL \windows\system
WAN.TSP \windows\system
PCMCIA/CardBus
--------------
SOCKETSV.VXD \windows\system
CBSS.VXD \windows\system
PCCARD.VXD \windows\system
Comm
----
VCD.VXD \windows\system\vmm32
VCOMM.VXD \windows\system\vmm32
VPD.VXD \windows\system\vmm32
SERENUM.VXD \windows\system
UNIMODEM.VXD \windows\system
IRCOMM.VXD \windows\system
IRENUM.VXD \windows\system
IRLAMP.VXD \windows\system
IRLAPFRM.VXD \windows\system
LPTENUM.VXD \windows\system
TAPI.DLL \windows\system
Video Capture
-------------
MSVFW32.DLL \windows\system
MSVIDEO.DLL \windows\system
VFWWDM32.SYS \windows\system32\drivers
VFWWDM.DRV \windows\system
Pen
---
PKPD.DLL \windows\system
PKPD32.DLL \windows\system
Printing
--------
SPOOLSS.DLL \windows\system
UNIDRV.DLL \windows\system
DIBENG.DLL \windows\system
and
CODE
The debug files found here are for use with Windows 98 Second Edition (SE).
This is a "delta" or change, from Windows 98. Only new, changed files appear here. If you do not find the files you are looking for and they appear in the original Windows 98 folder ("Dbg_sym"), use the original Windows 98 ones.
This is a "delta" or change, from Windows 98. Only new, changed files appear here. If you do not find the files you are looking for and they appear in the original Windows 98 folder ("Dbg_sym"), use the original Windows 98 ones.
Petr
I meant the version number, e.g. 4.10.2222
QUOTE (LLXX @ Nov 14 2006, 08:40 AM)
I meant the version number, e.g. 4.10.2222
So I gave you the answer, or do you need any additional information?
Petr
QUOTE (Petr @ Nov 14 2006, 08:00 AM)
QUOTE (LLXX @ Nov 14 2006, 08:40 AM)
I meant the version number, e.g. 4.10.2222
So I gave you the answer, or do you need any additional information?
Petr
QUOTE (LLXX @ Nov 15 2006, 07:27 AM)
QUOTE (Petr @ Nov 14 2006, 08:00 AM)
QUOTE (LLXX @ Nov 14 2006, 08:40 AM)
I meant the version number, e.g. 4.10.2222
So I gave you the answer, or do you need any additional information?
Petr
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.
Petr
Edit: 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:
CODE
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.DLL
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.DLL
and this is the list of symbols in this folder:
CODE
1394BUS.SYM
ACPI.SYM
ADVAPI32.SYM
CBSS.SYM
CCPORT.SYM
CDVSD.SYM
CONFIGMG.SYM
DINPUT.SYM
DISKTSD.SYM
ESDI_506.SYM
GDI.SYM
HID.SYM
HIDCLASS.SYM
HIDPARSE.SYM
HIDUSB.SYM
IFSMGR.SYM
IOS.SYM
IRENUM.SYM
JOYHID.SYM
KBDHID.SYM
KERNEL32.SYM
KMIXER.SYM
KRNL386.SYM
KS.SYM
KSCLOCKF.SYM
KSDATA.SYM
KSINTERF.SYM
KSPROXY.SYM
KSVPINTF.SYM
MMCI.SYM
MOUHID.SYM
MSDV.SYM
MSKSSRV.SYM
NDIS.SYM
NTKERN.SYM
OHCI1394.SYM
OPENHCI.SYM
PCCARD.SYM
PCI.SYM
PORTCLS.SYM
PPPMAC.SYM
REMOTESP.SYM
RSVPSP.SYM
SCSIPORT.SYM
SECUR32.SYM
SETUPX.SYM
STREAM.SYM
SWMIDI.SYM
SYSAUDIO.SYM
TAPI32.SYM
TAPISRV.SYM
UDF.SYM
UHCD.SYM
UNIMODEM.SYM
USBAUDIO.SYM
USBD.SYM
USBHUB.SYM
USBSER.SYM
USER.SYM
USER32.SYM
VCOMM.SYM
VDD.SYM
VDHCP.SYM
VFWWDM.SYM
VFWWDM32.SYM
VIP.SYM
VMM.SYM
VMOUSE.SYM
VNBT.SYM
VPICD.SYM
VREDIR.SYM
VTCP.SYM
VWIN32.SYM
VXDLDR.SYM
WAN.SYM
WDMAUD.SYM
WDMMDMLD.SYM
WMIDRV.SYM
ACPI.SYM
ADVAPI32.SYM
CBSS.SYM
CCPORT.SYM
CDVSD.SYM
CONFIGMG.SYM
DINPUT.SYM
DISKTSD.SYM
ESDI_506.SYM
GDI.SYM
HID.SYM
HIDCLASS.SYM
HIDPARSE.SYM
HIDUSB.SYM
IFSMGR.SYM
IOS.SYM
IRENUM.SYM
JOYHID.SYM
KBDHID.SYM
KERNEL32.SYM
KMIXER.SYM
KRNL386.SYM
KS.SYM
KSCLOCKF.SYM
KSDATA.SYM
KSINTERF.SYM
KSPROXY.SYM
KSVPINTF.SYM
MMCI.SYM
MOUHID.SYM
MSDV.SYM
MSKSSRV.SYM
NDIS.SYM
NTKERN.SYM
OHCI1394.SYM
OPENHCI.SYM
PCCARD.SYM
PCI.SYM
PORTCLS.SYM
PPPMAC.SYM
REMOTESP.SYM
RSVPSP.SYM
SCSIPORT.SYM
SECUR32.SYM
SETUPX.SYM
STREAM.SYM
SWMIDI.SYM
SYSAUDIO.SYM
TAPI32.SYM
TAPISRV.SYM
UDF.SYM
UHCD.SYM
UNIMODEM.SYM
USBAUDIO.SYM
USBD.SYM
USBHUB.SYM
USBSER.SYM
USER.SYM
USER32.SYM
VCOMM.SYM
VDD.SYM
VDHCP.SYM
VFWWDM.SYM
VFWWDM32.SYM
VIP.SYM
VMM.SYM
VMOUSE.SYM
VNBT.SYM
VPICD.SYM
VREDIR.SYM
VTCP.SYM
VWIN32.SYM
VXDLDR.SYM
WAN.SYM
WDMAUD.SYM
WDMMDMLD.SYM
WMIDRV.SYM
Do you need any more information?
Petr
In other words, the symbols would probably not work for newer versions (e.g. 4.10.2225 ESDI_506.PDR)
QUOTE (LLXX @ Nov 13 2006, 07:16 PM)
QUOTE (Petr @ Nov 9 2006, 02:33 AM)
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?
QUOTE (tErmY @ Nov 16 2006, 01:38 PM)
QUOTE (LLXX @ Nov 13 2006, 07:16 PM)
QUOTE (Petr @ Nov 9 2006, 02:33 AM)
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 ?
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?
Petr
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 symbols
2. Generate wdf file using e.g. 4.10.2225 dll version without symbols
3. 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
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?
Petr
QUOTE (LLXX @ Nov 16 2006, 07:19 AM)
In 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 symbols
2. Generate wdf file using e.g. 4.10.2225 dll version without symbols
3. 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
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)
This is a "lo-fi" version of our main content. To view the full version with more information, formatting and images, please click here.