Conference decwet::windows-nt

Hi Adrian,

>>Can anyone point me to a source for the Digital driver .SYM files for the
>>DEFPA.SYS and LATS.SYS drivers for Windows NT?
>>
>>Are they available for each DEFPA and PathWORKS kits for Windows NT?

Funny that after all of the Notes we've exchanged about the FDDI adapters that
you'd choose to post a DEFPA driver-related question in this forum.

Anyway, there is no DEFPA.SYM file available.  What problem are you running
into that would require a symbol file?

- Larry

Hi Larry, ;]

>Funny that after all of the Notes we've exchanged about the FDDI adapters
that
>you'd choose to post a DEFPA driver-related question in this forum.

Good point. Anyway, while I've got you here...

>Anyway, there is no DEFPA.SYM file available.  What problem are you running
>into that would require a symbol file?

Microsoft Asia-Pacific support center haven't got the DEFPA.SYM (and LATS.SYM,
but you won't be able to help me with that) for a crash we've been working
which looks like an NT problem. They've requested we supply as a favour to
assist their engineers if it's required. But... if they are out of luck then
that's fine.

Thanks & regards,
Adrian

[Posted by WWW Notes gateway]

Hi Adrian,

>>>Anyway, there is no DEFPA.SYM file available.  What problem are you running
>>>into that would require a symbol file?
>>
>>Microsoft Asia-Pacific support center haven't got the DEFPA.SYM (and LATS.SYM,
>>but you won't be able to help me with that) for a crash we've been working
>>which looks like an NT problem. They've requested we supply as a favour to
>>assist their engineers if it's required. But... if they are out of luck then
>>that's fine.

We don't build .SYM files for the NT drivers that we release.  Frankly, I don't
even know how to do that.  We do build "checked" versions of drivers during
development but these are .SYS files which contain debugging information and do
not get released.  The .SYS files that DO get released are called "free
builds".

If you're using the DEFPA.SYS driver that's bundled in 3.51 or 4.0, it's a
different driver than what we're shipping, so you should be able to get symbol
files off the CD, or from Microsoft.

Regards,
   Larry

    Re .3, when you build a checked version of the driver or any kernel
    components, the symbols are included in the image.  Thus, the big size. 
    There is a tool called splitsym.exe that will split the symbols into a
    separate file and leave the checked driver with a smaller foot-print.
    
    This would come in handy during debug since you'd load a smaller driver
    image on the target system and be able to get to its symbols on the
    host where kd runs.
    
    --svb

>>    Re .3, when you build a checked version of the driver or any kernel
>>    components, the symbols are included in the image.  Thus, the big size. 
>>    There is a tool called splitsym.exe that will split the symbols into a
>>    separate file and leave the checked driver with a smaller foot-print.
>>    
>>    This would come in handy during debug since you'd load a smaller driver
>>    image on the target system and be able to get to its symbols on the
>>    host where kd runs.

This question (about .SYM files) comes up every so often.  Where do I get
splitsym.exe?  I checked the SDK, DDK, and Visual C++ bin paths but didn't find
it.

Thanks,
   Larry

    Re .5, splitsym.exe can be found in the \idw directory of a checked NT
    CDROM (usually from MSDN kit).  \idw, in general, has quite an eclectic
    collection of neat tools, but not necessarily documented though.
    
    --svb

Thanks!

/l