More on IDE and build.bat, and Windows Mediocre Edition

I have been building NT drivers by calling a batch file from the IDE for
years. In fact, I have mostly built NT drivers under Win98SE (gasp!) using
this method. I have never had a problem using Win98. I simply set up all
the proper environment variables in my batch file, and as far as I could
tell, build.exe was none the wiser. To be fair, the release build was
always built “properly,” so my little indiscretion never affected the actual
binaries sent to the customer.

This week I bought a new system. It came with lots of memory, a fast
processor, and a rather ugly black and silver case. Inside was lurking
Windows ME. No problem, I thought, I’ll just keep using my batch file
called from the IDE to build my NT drivers. Wrooooong.

Millennium Edition has 256 bytes of environment space allocated for a batch
file. 256 BYTES. Now, I don’t know about you, but by the time you get
everything set up for a driver build, 256 bytes does not go very far.

Easy - just add:

shell=c:\command.com /e:4096 /p

To config.sys. Wrong again. ME does not use config.sys.

So I check the knowledge base:

http://support.microsoft.com/support/kb/articles/Q261/8/25.ASP

It says, either put your environment variable in your autoexec.bat, or
create a shortcut to your batch file in which you set the environment size.
Well, you can’t call setenv.bat from autoexec.bat. It gets removed
automatically by ME. And I could not figure out how to the IDE to use the
shortcut settings rather than directly calling the batch file.

Ok. No problem. I created a second batch file containing:

c:\windows\command.com /e:4096 /c runbuild.bat %1

And call that batch file from the IDE. Great! Cool! I get a compile! And
maybe four or five before I run out of system memory. Turns out, every time
I execute, I get another copy of winoldap in my task manager list. I have
to keep going in and killing them to keep working. Not an acceptable
solution.

Gotta love this progress…

Now, most of you are saying, “Just upgrade to Win2K.” I really am not
enthusiastic about spending another $150.00 to $200.00 USD on top of just
buying MSVC 6 and MSDN. Not for something this minor. Plus, I don’t know
which of the applications and devices I have will work with Win2K after an
upgrade. I spent almost a week getting ME set up to my satisfaction. I
would rather just set up my batch file to be called from the IDE and go on
with life.

Anyone have any ideas? I don’t have any cherry bombs, so that idea is
out…

Thank,

Evan Hillman


You are currently subscribed to ntdev as: $subst(‘Recip.EmailAddr’)
To unsubscribe send a blank email to leave-ntdev-$subst(‘Recip.MemberIDChar’)@lists.osr.com

Hi Evan,

That thing about seeing winoldapp in your task list. I have seen that before
on a Win98 system too. It was actually caused by setenv.bat loading doskey.
Since you are doing builds from IDE, you won’t need doskey so maybe you can
REM it out in the batch files. Worth a try, don’t know if this IS the
problem in your configuration though.

Hope it helps

----- Original Message -----
From: “Evan Hillman”
To: “NT Developers Interest List”
Sent: Friday, April 13, 2001 11:13 AM
Subject: [ntdev] More on IDE and build.bat, and Windows Mediocre Edition

> I have been building NT drivers by calling a batch file from the IDE for
> years. In fact, I have mostly built NT drivers under Win98SE (gasp!) using
> this method. I have never had a problem using Win98. I simply set up all
> the proper environment variables in my batch file, and as far as I could
> tell, build.exe was none the wiser. To be fair, the release build was
> always built “properly,” so my little indiscretion never affected the
actual
> binaries sent to the customer.
>
>
> This week I bought a new system. It came with lots of memory, a fast
> processor, and a rather ugly black and silver case. Inside was lurking
> Windows ME. No problem, I thought, I’ll just keep using my batch file
> called from the IDE to build my NT drivers. Wrooooong.
>
> Millennium Edition has 256 bytes of environment space allocated for a
batch
> file. 256 BYTES. Now, I don’t know about you, but by the time you get
> everything set up for a driver build, 256 bytes does not go very far.
>
> Easy - just add:
>
> shell=c:\command.com /e:4096 /p
>
> To config.sys. Wrong again. ME does not use config.sys.
>
> So I check the knowledge base:
>
> http://support.microsoft.com/support/kb/articles/Q261/8/25.ASP
>
> It says, either put your environment variable in your autoexec.bat, or
> create a shortcut to your batch file in which you set the environment
size.
> Well, you can’t call setenv.bat from autoexec.bat. It gets removed
> automatically by ME. And I could not figure out how to the IDE to use the
> shortcut settings rather than directly calling the batch file.
>
> Ok. No problem. I created a second batch file containing:
>
> c:\windows\command.com /e:4096 /c runbuild.bat %1
>
> And call that batch file from the IDE. Great! Cool! I get a compile!
And
> maybe four or five before I run out of system memory. Turns out, every
time
> I execute, I get another copy of winoldap in my task manager list. I have
> to keep going in and killing them to keep working. Not an acceptable
> solution.
>
> Gotta love this progress…
>
> Now, most of you are saying, “Just upgrade to Win2K.” I really am not
> enthusiastic about spending another $150.00 to $200.00 USD on top of just
> buying MSVC 6 and MSDN. Not for something this minor. Plus, I don’t know
> which of the applications and devices I have will work with Win2K after an
> upgrade. I spent almost a week getting ME set up to my satisfaction. I
> would rather just set up my batch file to be called from the IDE and go on
> with life.
>
> Anyone have any ideas? I don’t have any cherry bombs, so that idea is
> out…
>
> Thank,
>
> Evan Hillman
>
>
> —
> You are currently subscribed to ntdev as: xxxxx@hotmail.com
> To unsubscribe send a blank email to leave-ntdev-$subst(‘Recip.MemberIDChar’)@lists.osr.com
>


You are currently subscribed to ntdev as: $subst(‘Recip.EmailAddr’)
To unsubscribe send a blank email to leave-ntdev-$subst(‘Recip.MemberIDChar’)@lists.osr.com

Norman,

Thanks - I edited setenv.bat in the DDK, commented out the doskey lines, and
it fixed that particular problem. I would never have figured this out for
myself! The only downside is reinstalling the DDK and having the change
overwritten, but I’ll live with that.

I’m not all that thrilled with the stability of ME, so I may be upgrading
anyway in the interests of long-term sanity. I just started a new job
Monday, here it is Friday, and all I have to show for my first week of work
is a compiled example. Not much of a first impression!

Thanks again,

Evan Hillman

-----Original Message-----
From: xxxxx@lists.osr.com
[mailto:xxxxx@lists.osr.com]On Behalf Of Noman Smith
Sent: Friday, April 13, 2001 2:57 PM
To: NT Developers Interest List
Subject: [ntdev] Re: More on IDE and build.bat, and Windows Mediocre
Edition

Hi Evan,

That thing about seeing winoldapp in your task list. I have seen that before
on a Win98 system too. It was actually caused by setenv.bat loading doskey.
Since you are doing builds from IDE, you won’t need doskey so maybe you can
REM it out in the batch files. Worth a try, don’t know if this IS the
problem in your configuration though.

Hope it helps


You are currently subscribed to ntdev as: $subst(‘Recip.EmailAddr’)
To unsubscribe send a blank email to leave-ntdev-$subst(‘Recip.MemberIDChar’)@lists.osr.com

Well , I wont tell you to upgrade to Win2k … clearly is not a good
investments for you. Im just curious how you debug your NT kernel components
under 98 & how you test them in a real life enviroment . I guess you dont.

----- Original Message -----
From: “Evan Hillman”
To: “NT Developers Interest List”
Sent: Friday, April 13, 2001 9:13 PM
Subject: [ntdev] More on IDE and build.bat, and Windows Mediocre Edition

> I have been building NT drivers by calling a batch file from the IDE for
> years. In fact, I have mostly built NT drivers under Win98SE (gasp!) using
> this method. I have never had a problem using Win98. I simply set up all
> the proper environment variables in my batch file, and as far as I could
> tell, build.exe was none the wiser. To be fair, the release build was
> always built “properly,” so my little indiscretion never affected the
actual
> binaries sent to the customer.
>
>
> This week I bought a new system. It came with lots of memory, a fast
> processor, and a rather ugly black and silver case. Inside was lurking
> Windows ME. No problem, I thought, I’ll just keep using my batch file
> called from the IDE to build my NT drivers. Wrooooong.
>
> Millennium Edition has 256 bytes of environment space allocated for a
batch
> file. 256 BYTES. Now, I don’t know about you, but by the time you get
> everything set up for a driver build, 256 bytes does not go very far.
>
> Easy - just add:
>
> shell=c:\command.com /e:4096 /p
>
> To config.sys. Wrong again. ME does not use config.sys.
>
> So I check the knowledge base:
>
> http://support.microsoft.com/support/kb/articles/Q261/8/25.ASP
>
> It says, either put your environment variable in your autoexec.bat, or
> create a shortcut to your batch file in which you set the environment
size.
> Well, you can’t call setenv.bat from autoexec.bat. It gets removed
> automatically by ME. And I could not figure out how to the IDE to use the
> shortcut settings rather than directly calling the batch file.
>
> Ok. No problem. I created a second batch file containing:
>
> c:\windows\command.com /e:4096 /c runbuild.bat %1
>
> And call that batch file from the IDE. Great! Cool! I get a compile!
And
> maybe four or five before I run out of system memory. Turns out, every
time
> I execute, I get another copy of winoldap in my task manager list. I have
> to keep going in and killing them to keep working. Not an acceptable
> solution.
>
> Gotta love this progress…
>
> Now, most of you are saying, “Just upgrade to Win2K.” I really am not
> enthusiastic about spending another $150.00 to $200.00 USD on top of just
> buying MSVC 6 and MSDN. Not for something this minor. Plus, I don’t know
> which of the applications and devices I have will work with Win2K after an
> upgrade. I spent almost a week getting ME set up to my satisfaction. I
> would rather just set up my batch file to be called from the IDE and go on
> with life.
>
> Anyone have any ideas? I don’t have any cherry bombs, so that idea is
> out…
>
> Thank,
>
> Evan Hillman
>
>
> —
> You are currently subscribed to ntdev as: danp@jb.rdsor.ro
> To unsubscribe send a blank email to leave-ntdev-$subst(‘Recip.MemberIDChar’)@lists.osr.com
>


You are currently subscribed to ntdev as: $subst(‘Recip.EmailAddr’)
To unsubscribe send a blank email to leave-ntdev-$subst(‘Recip.MemberIDChar’)@lists.osr.com

Dan,

Correct, I don’t debug or test under Win98 or WinME. For that matter, I
never test drivers on the same machine I develop them on. Too much risk of
blowing everything away with a kernel-mode error.

I have always had one machine for development, and a second for test. My
test machine currently dual-boots WinNT and Win2K so I can test my drivers.

I stuck the Win2K CD in my development machine, just for laughs. I got a
list of incompatible software and drivers requiring upgrade longer than I
care to contemplate. Like anything else, I have to decide when the pain of
change outweighs the pain of staying the same. I have a source formatting
program called CDoc I like to use. It won’t run under ME because there are
not enough files handles in DOS mode. CDoc requires 12, I believe, and ME
has less available.

I’m sure I will eventually find a web page telling me how to trick ME into
doing useful things. Till then, I’ll just whine.

-Evan Hillman

-----Original Message-----
From: xxxxx@lists.osr.com
[mailto:xxxxx@lists.osr.com]On Behalf Of Dan Partelly
Sent: Friday, April 13, 2001 12:28 PM
To: NT Developers Interest List
Subject: [ntdev] Re: More on IDE and build.bat, and Windows Mediocre
Edition

Well , I wont tell you to upgrade to Win2k … clearly is not a good
investments for you. Im just curious how you debug your NT kernel components
under 98 & how you test them in a real life enviroment . I guess you dont.


You are currently subscribed to ntdev as: $subst(‘Recip.EmailAddr’)
To unsubscribe send a blank email to leave-ntdev-$subst(‘Recip.MemberIDChar’)@lists.osr.com