Re: Target machine requirements for debugging
From: Dave August (august_at_NOSPAMacmesi.com)
Date: 10/25/04
- Next message: Dave August: "Re: Compiling a WDM driver using .NET 2003"
- Previous message: Shalini: "HCT Tests Submission"
- In reply to: Don Burn: "Re: Target machine requirements for debugging"
- Next in thread: Pavel A.: "Re: Target machine requirements for debugging"
- Messages sorted by: [ date ] [ thread ]
Date: Mon, 25 Oct 2004 15:02:12 -0700
Goodie,
Well Don is right on one hand,
But me, I come at it from a whole different end, find the scummiest,
junkiest box ya can, you know an old beat up 400MHZ clunker with 128MB, ,
really bad display adaptor...a funkey slow 20GIG drive or a couple of
OOOLLLDD 10Giggers..(hell one of my targets has 2, 4 gig drives in it..)
Dual boot it on 2K and XP and debug away( I actually have one box that
boots, 98 or ME or 2K)... FYI I do agree with Don on the dual processor
thing, I have an ancient dual 100mhz machine I use to make sure the
multi-processor stuff is OK...
Oh yeah get Norton Ghost too, ya GOTTA test from a clean install a LOT...
Dave (who's been hacking XPe lately)
"Don Burn" <burn@stopspam.acm.org> wrote in message
news:10nndut4j8ucr7f@corp.supernews.com...
> First your target machine should be multi-processor (or at least
> hyper-threaded). There is a general rule that the more processors the
> more
> threading and syncronization problems you will find. Second consider
> getting an AMD64 for the testbed so you can test your driver in both 32
> amd
> 64 bit mode OS'es.
>
> Personnally, I have used KVM switches and don't like them, there is a
> distaction when you toggle from the testbed to the dev system and back. I
> haven't tried it recently and since 2003 and XP both support terminal
> sessions, you might be ok with that now.
>
> Finally, I would add more RAM, it is cheap these days, and there are
> plenty
> of times it is helpful. Creating a circular log of data for debugging, or
> trying to run some of the enterprise app's of Microsoft quickly consume
> RAM.
>
>
> --
> Don Burn (MVP, Windows DDK)
> Windows 2k/XP/2k3 Filesystem and Driver Consulting
> Remove StopSpam from the email to reply
>
> "Good_Ol_glr" <sbnte021@coxDELETE_THIS.net> wrote in message
> news:957F496C-AE18-4E1F-9112-928B15533142@microsoft.com...
>> I am new to windows drivers & debugging. I will be debugging interfeces
>> to
>> external devices - USB, PCI,...
>> I get that - practically - I need a second machine as a target. My
>> funds
>> and office space not being infinite, I seek its minimum.
>> My host is AMD64 2.4 GHz, 1GBy RAM, 80 GBy disk...( I am happy with
>> this.)
>> About a reasonable target, my guesses :
>> * 256 Mby RAM - I won't be running lots of apps
>> * 1.8 GHz AMD/Pentium, - speed isn't important
>> * 80GBy disk for all those checked OS target systems
>> ...and my hopes ...
>> * I can switch using the same screen,keyboard,mouse
>> What do all you veterans think ?
>
>
- Next message: Dave August: "Re: Compiling a WDM driver using .NET 2003"
- Previous message: Shalini: "HCT Tests Submission"
- In reply to: Don Burn: "Re: Target machine requirements for debugging"
- Next in thread: Pavel A.: "Re: Target machine requirements for debugging"
- Messages sorted by: [ date ] [ thread ]
Relevant Pages
|
