My first WinHEC was 2008. I really enjoyed it.
Did it get replaced or what’s the story?
WINHEC, the World Indigenous Nations Higher Education Consortium, is
alive and well.
The other WINHEC, not so much. 2008 appears to have been the end of the road.
Mark Roddy
On Wed, May 2, 2012 at 11:55 AM, wrote:
> My first WinHEC was 2008. ?I really enjoyed it.
>
> Did it get replaced or what’s the story?
>
> —
> NTDEV is sponsored by OSR
>
> For our schedule of WDF, WDM, debugging and other seminars visit:
> http://www.osr.com/seminars
>
> To unsubscribe, visit the List Server section of OSR Online at http://www.osronline.com/page.cfm?name=ListServer
This past year, //build/ was where the winhec type content was presented
d
debt from my phone
From: xxxxx@hotmail.com
Sent: 5/2/2012 8:57 AM
To: Windows System Software Devs Interest List
Subject: [ntdev] Off Topic: But what happened to WinHEC?
My first WinHEC was 2008. I really enjoyed it.
Did it get replaced or what’s the story?
NTDEV is sponsored by OSR
For our schedule of WDF, WDM, debugging and other seminars visit:
http://www.osr.com/seminars
To unsubscribe, visit the List Server section of OSR Online at http://www.osronline.com/page.cfm?name=ListServer
Thanks Doron!
I wish I had known about it. Looking at their site it looks a lot more software based than the old WinHEC format. Although I’ve been slowly migrating my skills closer to hardware I’m always looking for more information on how Windows expects things to operate. I really enjoyed the driver writer’s workshops at WinHEC and occasionally check to see if another WinHEC has been scheduled.
Hopefully I haven’t derailed too far from the purpose of this forum. I just figured some folks here might know more about what happened to WinHEC and if it had been replaced or there were other conferences covering material more in line with the subjects often brought up here.
I will probably go to whatever the next conference is, but I skipped
Build since one of the nicest things about WinHEC was that it brought
together the driver and hardware communities and was small enough to
allow networking. The mega-conference approach means the only value
provided are the sessions, which to me was not the major draw of WinHEC>
Don Burn
Windows Filesystem and Driver Consulting
Website: http://www.windrvr.com
Blog: http://msmvps.com/blogs/WinDrvr
“xxxxx@hotmail.com” wrote in message
news:xxxxx@ntdev:
> Thanks Doron!
>
> I wish I had known about it. Looking at their site it looks a lot more software based than the old WinHEC format. Although I’ve been slowly migrating my skills closer to hardware I’m always looking for more information on how Windows expects things to operate. I really enjoyed the driver writer’s workshops at WinHEC and occasionally check to see if another WinHEC has been scheduled.
>
> Hopefully I haven’t derailed too far from the purpose of this forum. I just figured some folks here might know more about what happened to WinHEC and if it had been replaced or there were other conferences covering material more in line with the subjects often brought up here.
The emphasis being on “winhec TYPE” content … as in “the TYPE of content you might see at WinHEC, but with even less depth, presented by fewer developers, and with less specifics.”
Sorry Doron…No offense to you or your team. But build wasn’t exactly chock-a-block with juicy details, or even with dev-to-dev networking opportunities. Full disclosure: I was in India at the time, so *I* didn’t go… though I *have* watched a *lot* of the session videos, so I think I’m in a fair position to comment about the content.
There are rumors starting to percolate about another conference being held this year…
Peter
OSR
Remember how you described how sinofsky runs a release and how disclosure is done? //build/ is a direct reflection of that. Also, conventions are way expensive to run and i would guess we lose money on them, do given all of the belt tightening, it is not surprising that pdc and winhec would merge
d
debt from my phone
From: xxxxx@osr.com
Sent: 5/2/2012 1:11 PM
To: Windows System Software Devs Interest List
Subject: RE:[ntdev] Off Topic: But what happened to WinHEC?
The emphasis being on “winhec TYPE” content … as in “the TYPE of content you might see at WinHEC, but with even less depth, presented by fewer developers, and with less specifics.”
Sorry Doron…No offense to you or your team. But build wasn’t exactly chock-a-block with juicy details, or even with dev-to-dev networking opportunities. Full disclosure: I was in India at the time, so *I* didn’t go… though I *have* watched a *lot* of the session videos, so I think I’m in a fair position to comment about the content.
There are rumors starting to percolate about another conference being held this year…
Peter
OSR
NTDEV is sponsored by OSR
For our schedule of WDF, WDM, debugging and other seminars visit:
http://www.osr.com/seminars
To unsubscribe, visit the List Server section of OSR Online at http://www.osronline.com/page.cfm?name=ListServer
//build/ looks very “prefocey” or unixy. Isn’t Microsoft supposed to use
\build?
Calvin
On Wed, May 2, 2012 at 1:39 PM, Doron Holan wrote:
> Remember how you described how sinofsky runs a release and how
> disclosure is done? //build/ is a direct reflection of that. Also,
> conventions are way expensive to run and i would guess we lose money on
> them, do given all of the belt tightening, it is not surprising that pdc
> and winhec would merge
>
> d
>
> debt from my phone
> ------------------------------
> From: xxxxx@osr.com
> Sent: 5/2/2012 1:11 PM
>
> To: Windows System Software Devs Interest List
> Subject: RE:[ntdev] Off Topic: But what happened to WinHEC?
>
>
>
> The emphasis being on “winhec TYPE” content … as in “the TYPE of content
> you might see at WinHEC, but with even less depth, presented by fewer
> developers, and with less specifics.”
>
> Sorry Doron…No offense to you or your team. But build wasn’t exactly
> chock-a-block with juicy details, or even with dev-to-dev networking
> opportunities. Full disclosure: I was in India at the time, so I didn’t
> go… though I have watched a lot of the session videos, so I think I’m
> in a fair position to comment about the content.
>
> There are rumors starting to percolate about another conference being held
> this year…
>
> Peter
> OSR
>
>
> —
> NTDEV is sponsored by OSR
>
> For our schedule of WDF, WDM, debugging and other seminars visit:
> http://www.osr.com/seminars
>
> To unsubscribe, visit the List Server section of OSR Online at
> http://www.osronline.com/page.cfm?name=ListServer
>
>
> —
> NTDEV is sponsored by OSR
>
> For our schedule of WDF, WDM, debugging and other seminars visit:
> http://www.osr.com/seminars
>
> To unsubscribe, visit the List Server section of OSR Online at
> http://www.osronline.com/page.cfm?name=ListServer
>
I think the forward slashes were supposed to evoke a URL, so HTTP’ey
From: xxxxx@lists.osr.com [mailto:xxxxx@lists.osr.com] On Behalf Of Calvin Guan (news)
Sent: Wednesday, May 02, 2012 2:31 PM
To: Windows System Software Devs Interest List
Subject: Re: [ntdev] Off Topic: But what happened to WinHEC?
//build/ looks very “prefocey” or unixy. Isn’t Microsoft supposed to use \build<file:>?
Calvin
On Wed, May 2, 2012 at 1:39 PM, Doron Holan > wrote:
Remember how you described how sinofsky runs a release and how disclosure is done? //build/ is a direct reflection of that. Also, conventions are way expensive to run and i would guess we lose money on them, do given all of the belt tightening, it is not surprising that pdc and winhec would merge
d
debt from my phone
________________________________
From: xxxxx@osr.commailto:xxxxx
Sent: 5/2/2012 1:11 PM
To: Windows System Software Devs Interest List
Subject: RE:[ntdev] Off Topic: But what happened to WinHEC?
The emphasis being on “winhec TYPE” content … as in “the TYPE of content you might see at WinHEC, but with even less depth, presented by fewer developers, and with less specifics.”
Sorry Doron…No offense to you or your team. But build wasn’t exactly chock-a-block with juicy details, or even with dev-to-dev networking opportunities. Full disclosure: I was in India at the time, so I didn’t go… though I have watched a lot of the session videos, so I think I’m in a fair position to comment about the content.
There are rumors starting to percolate about another conference being held this year…
Peter
OSR
—
NTDEV is sponsored by OSR
For our schedule of WDF, WDM, debugging and other seminars visit:
http://www.osr.com/seminars
To unsubscribe, visit the List Server section of OSR Online at http://www.osronline.com/page.cfm?name=ListServer
—
NTDEV is sponsored by OSR
For our schedule of WDF, WDM, debugging and other seminars visit:
http://www.osr.com/seminars
To unsubscribe, visit the List Server section of OSR Online at http://www.osronline.com/page.cfm?name=ListServer
— NTDEV is sponsored by OSR For our schedule of WDF, WDM, debugging and other seminars visit: http://www.osr.com/seminars To unsubscribe, visit the List Server section of OSR Online at http://www.osronline.com/page.cfm?name=ListServer</mailto:xxxxx></file:>
>//build/ looks very “prefocey” or unixy. Isn’t Microsoft supposed to use
\build?
Just be grateful it was not called “Heroes Happen Here” or something like that.
Or that you had to sing songs about how you’re a PC.
mm
-----Original Message-----
From: xxxxx@lists.osr.com
[mailto:xxxxx@lists.osr.com] On Behalf Of xxxxx@broadcom.com
Sent: Wednesday, May 02, 2012 2:43 PM
To: Windows System Software Devs Interest List
Subject: RE:[ntdev] Off Topic: But what happened to WinHEC?
//build/ looks very “prefocey” or unixy. Isn’t Microsoft supposed to use
\build?
Just be grateful it was not called “Heroes Happen Here” or something like
that.
NTDEV is sponsored by OSR
For our schedule of WDF, WDM, debugging and other seminars visit:
http://www.osr.com/seminars
To unsubscribe, visit the List Server section of OSR Online at
http://www.osronline.com/page.cfm?name=ListServer
// DDEF TYPE=“BUILD”
For some of us, // predates HTTP. By about 30 years.
(I used to be able to write very complex JCL)
joe
>//build/ looks very “prefocey” or unixy. Isn’t Microsoft supposed to use
\build?Just be grateful it was not called “Heroes Happen Here” or something like
that.
NTDEV is sponsored by OSR
For our schedule of WDF, WDM, debugging and other seminars visit:
http://www.osr.com/seminarsTo unsubscribe, visit the List Server section of OSR Online at
http://www.osronline.com/page.cfm?name=ListServer
And it was nice that the videos were available, although after the first week of watching them it did require a bit more caffeine to stay awake through them (regardless of how interesting the content or engaging the presenter).
JCL. OMG that takes me back. Scary then, still scary now…
OMG is RIGHT. I didn’t even *recognize* Joe’s reference until Maria named it.
OH, my eyes… MY EYES!!!
There’s a great example on Wikipedia that brought back a lot of scary memories (but no WAY I could have written this from memory):
//IS198CPY JOB (IS198T30500),‘COPY JOB’,CLASS=L,MSGCLASS=X
//COPY01 EXEC PGM=IEBGENER
//SYSPRINT DD SYSOUT=*
//SYSUT1 DD DSN=OLDFILE,DISP=SHR
//SYSUT2 DD DSN=NEWFILE,
// DISP=(NEW,CATLG,DELETE),
// SPACE=(CYL,(40,5),RLSE),
// DCB=(LRECL=115,BLKSIZE=1150)
//SYSIN DD DUMMY
For those of you who never had the privilege of working on an IBM 360, this was how you copied a file. Seriously. You might think “copy OLDFILE NEWFILE” would be enough… but NO!
Peter
OSR
(and let us not forget //*)
I got a lot from Build. Maybe the content leaned more towards pdc than winhec but there was a lot of it that was new because of WinRT. I also really appreciate that it’s available on line. Compared to how Apple treats their development community when their wwdc sells out in 2 hours and if you don’t get in you’re out of luck, MS does a great job.
Plus I love my tablet.
Sorry, but the presentations are at best WinHEC Lite, and most of us who
have been in the community for a long time felt WinHEC already was
“Lite”. I considered the PDC to be worthless for a long time, and
adding a little WinHEC content and saying it solves the needs of the
community is ridiculous.
Don Burn
Windows Filesystem and Driver Consulting
Website: http://www.windrvr.com
Blog: http://msmvps.com/blogs/WinDrvr
“xxxxx@gmail.com” wrote in message
news:xxxxx@ntdev:
> I got a lot from Build. Maybe the content leaned more towards pdc than winhec but there was a lot of it that was new because of WinRT. I also really appreciate that it’s available on line. Compared to how Apple treats their development community when their wwdc sells out in 2 hours and if you don’t get in you’re out of luck, MS does a great job.
>
> Plus I love my tablet.
> //SYSUT2 DD DSN=NEWFILE,
// DISP=(NEW,CATLG,DELETE),
// SPACE=(CYL,(40,5),RLSE),
// DCB=(LRECL=115,BLKSIZE=1150)
//SYSIN DD DUMMYFor those of you who never had the privilege of working on an IBM 360
My older Russian friends worked on Soviet IBM 360 clones (also blue boxes 
), and they called this language: “bird’s language”.
“dd” seems to be the same as in UNIXen though Was “dd” the only way to copy the file on IBM 360?
–
Maxim S. Shatskih
Windows DDK MVP
xxxxx@storagecraft.com
http://www.storagecraft.com
Maxim S. Shatskih wrote:
> //SYSUT2 DD DSN=NEWFILE,
> // DISP=(NEW,CATLG,DELETE),
> // SPACE=(CYL,(40,5),RLSE),
> // DCB=(LRECL=115,BLKSIZE=1150)
> //SYSIN DD DUMMY
>
> For those of you who never had the privilege of working on an IBM 360
My older Russian friends worked on Soviet IBM 360 clones (also blue boxes“dd” seems to be the same as in UNIXen though
The DD here means “data definition”. It is defining what kind of device
or file is bound to the name “SYSUT2” or “SYSIN”. The command to be run
was identified earlier in the job:
//COPY01 EXEC PGM=IEBGENER
One might ask why the “copy” command would be called “IEBGENER”, but one
would not get an answer. The other lines are just binding devices or
files to the names used by the copy command (SYSUT1 for input, SYSUT2
for output, SYSIN and SYSPRINT for the equivalent of stdin and stdout).
–
Tim Roberts, xxxxx@probo.com
Providenza & Boekelheide, Inc.
>> //SYSUT2 DD DSN=NEWFILE,
> // DISP=(NEW,CATLG,DELETE),
> // SPACE=(CYL,(40,5),RLSE),
> // DCB=(LRECL=115,BLKSIZE=1150)
> //SYSIN DD DUMMY
Was the “Caps Lock” stuck? I feel nervous when reading all caps.
Nope, that most likely was generated to a printer AFTER having been punched into cards, using the EBCDC character set, where lowercase was defined but seldom, if ever used. At that time you (we!?!?!) were lucky if you (we!?!?!) had a teletype, running at a MIGHTY SPEEDY 60 words per second, about 300 baud.
Gary Little
H (952) 223-1349
C (952) 454-4629
xxxxx@comcast.net
On May 11, 2012, at 12:29 PM, Calvin Guan (news) wrote:
>> //SYSUT2 DD DSN=NEWFILE,
>> // DISP=(NEW,CATLG,DELETE),
>> // SPACE=(CYL,(40,5),RLSE),
>> // DCB=(LRECL=115,BLKSIZE=1150)
>> //SYSIN DD DUMMYWas the “Caps Lock” stuck? I feel nervous when reading all caps.
— NTDEV is sponsored by OSR For our schedule of WDF, WDM, debugging and other seminars visit: http://www.osr.com/seminars To unsubscribe, visit the List Server section of OSR Online at http://www.osronline.com/page.cfm?name=ListServer