Loren,
In the past when a client of mine did not want to have VxD for their code
(win3.1) to work with win95, and full fledge driver for nt,instead a VDD…
I had email conversation with Matt, he encouraged to use his idea and code
from one of his great book “Sys programing secrets”, he is just a hell of
nice guy to put it mildly, so I dont think there is any right violation,
also the code up in Msj server does not have any copywrong stmt…
-prokash
----- Original Message -----
From: “Loren Wilton”
To: “Windows System Software Devs Interest List”
Sent: Friday, October 03, 2003 7:26 AM
Subject: [ntdev] Re: OT: Quiet dependency walker?
> Thanks for the info on this area, all. I haven’t found any command line
> switches to either the MS Depends or the one in MSJ (also called Depends)
> that will do more or less what I want, without writing a huge amount of
> filtering logic on the text output. However, the one in the MSJ came with
> source, and it should be a simple matter to hack that code into a DLL that
> can be called from Vise to do exactly what I want. So far as I know the
> example code in the MSJ article should permit modification and reuse of
the
> code or code parts. Probably easier than starting from scratch with
> toolhelp, which is the only real alternative I see.
>
> Loren
>
>
> ----- Original Message -----
> From: “Prokash Sinha”
> To: “Windows System Software Devs Interest List”
> Sent: Friday, October 03, 2003 7:07 AM
> Subject: [ntdev] Re: OT: Quiet dependency walker?
>
>
> > Arlie,
> > U r absolutely right I suppose. After I did hit the send button on the
> prev.
> > note, I thought that it was a gross misstatement. What I meant to say
> though
> > was that I’ve seen an article by Matt that had code also …
> >
> > This reminds me of one song during the early 80’s
> >
> > “One thing leads to another” … say what U mean …
> >
> > -prokash
> > ----- Original Message -----
> > From: “Arlie Davis”
> > To: “Windows System Software Devs Interest List”
> > Sent: Friday, October 03, 2003 6:41 AM
> > Subject: [ntdev] Re: OT: Quiet dependency walker?
> >
> >
> > > I believe Steve Miller would disagree with you. Steve wrote
> > > depends.exe, and depends.exe is shipped as part of MSVC / Visual
Studio.
> > > Matt’s a fine guy, but he didn’t write that dependency walker. (Maybe
> > > he wrote a different one – I don’t know.)
> > >
> > > Depends.exe has many command-line options, and a console mode. In
> > > console mode, it will interpret and act on command-line arguments,
print
> > > the result, then exit. You may be able to use this. However, this
may
> > > require shipping around a copy of depends.exe with your code, and I
> > > don’t think that’s kosher. I know it’s a long shot, but try asking
> > > Microsoft if you can do this – after all, you’re trying to reduce
> > > install problems on their own products.
> > >
> > > – arlie
> > >
> > >
> > > -----Original Message-----
> > > From: xxxxx@lists.osr.com
> > > [mailto:xxxxx@lists.osr.com] On Behalf Of Prokash Sinha
> > > Sent: Thursday, October 02, 2003 10:21 AM
> > > To: Windows System Software Devs Interest List
> > > Subject: [ntdev] Re: OT: Quiet dependency walker?
> > >
> > >
> > > IIRC, depends.exe was originally from Matt Pietrek. And I’ve seen
> > > example code in some Microsoft Journal, when he was almost a regular
> > > contributor. It uses toolhelp library. I would suggest looking at the
> > > Msj archieve for example to start with !!!
> > >
> > > -prokash
> > >
> > > ----- Original Message -----
> > > From: “Loren Wilton”
> > > To: “Windows System Software Devs Interest List”
> > > Sent: Thursday, October 02, 2003 4:00 AM
> > > Subject: [ntdev] OT: Quiet dependency walker?
> > >
> > >
> > > > Does anyone know of a program or DLL that will do essentially what
> > > > Depends does, but return an encoded result of something like “OK /
> > > > Missing DLL / Missing Entry Point?”
> > > >
> > > > I’m tired of distributing programs that don’t run on some antique
> > > > version
> > > of
> > > > Win95 or NT 4 that has never had a service pack applied, and I end
up
> > > > with
> > > a
> > > > missing entry point in mfc42.dll or some such, and of course it is
MY
> > > fault
> > > > because I shipped a BROKEN program.
> > > >
> > > > I’d like a tool I can run as part of the installer so I can crank
out
> > > > a message that says “Stupid youk – update this system to something
in
> > >
> > > > the last century if you expect new programs to run!”, and then abort
> > > > the install.
> > > >
> > > > Yes, I know I can just copy all the system DLLs into the bogus
target
> > > > system, after a few hundred lines of code to try to predict which
> > > > files
> > > are
> > > > actually older than the files I ship with the product. And
sometimes
> > > > this works. And sometimes the user ends up having to reinstall an
> > > > upgrade of Win95 (from Win 3.0) on a 386SX-16 as a result of copying
> > > > one of those files, and complains that I broke a perfectly good
system
> > >
> > > > that has never
> > > had
> > > > a problem.
> > > >
> > > > I’m tired of doing that. I just want to be able to tell them their
> > > antique
> > > > boatanchor needs to be professionally updated by a trip to
> > > > windowsupdate
> > > and
> > > > be done with it. But I only want to tell them that if my program
> > > > won’t
> > > run;
> > > > not just because they ought to.
> > > >
> > > > Loren
> > > >
> > > > (Rant off.)
>
>
> —
> Questions? First check the Kernel Driver FAQ at
http://www.osronline.com/article.cfm?id=256
>
> You are currently subscribed to ntdev as: xxxxx@garlic.com
> To unsubscribe send a blank email to xxxxx@lists.osr.com
>
>