[NHL] Lottery Draft Order

By Steffan
in The Sporting Arena

 Share

Recommended Posts

Grand Master

Steffan

Posted
Posted

http://espn.go.com/nhl/draftorder.html

1. Washington Capitals

2. Pittsburgh Penguins

3. Chicago Blackhawks

4. Columbus Blue Jackets

5. Phoenix Coyotes

6. New York Rangers

7. Florida Panthers

8. Carolina Hurricanes

9. Anaheim Mighty Ducks

10. Atlanta Thrashers

11. Los Angeles Kings

12. Minnesota Wild

13. Buffalo Sabres

14. Edmonton Oilers

Remainder TBD after playoffs

Link to comment
https://www.neowin.net/forum/topic/155413-nhl-lottery-draft-order/
Share on other sites
Grand Master

Fred Derf Veteran

Posted
  • Veteran
Posted

Here's the big question then...

Does Washington get to pick first again next year if there is no 2004/2005 season?

Or will they make all the kids, who would have been eligable in 2005, wait until the 2006 draft? That would result in a draft that was twice as thick as usual with Sydney Crosby topping the list to boot.

They better have a season just to avoid this problem! If I was GMing a somewhat cruddy team in 2005/2006 then I might be tempted to lose even more games for a better lottery spot.

Rising Star

IndianPimp99

Posted
Posted

Man, the Hawks got the lowest pick that was allowed for their record. Just like the regular season, at the bottom again.

Hopefully they'll be able to draft someone that has promise and can play well with Tuomo. I wouldn't mind seeing them form a duo comprable to Chelios and Roenick (except for the trading part).

Damn Wirtz!!

Experienced

LRoling

Posted
Posted

Yeah, but Tuomo isn't as good as he has been predicted. I watched many Hawks games, being from the Chicagoland area, and they are my second favorite team, behind the Avalanche due to the fact my Dad has season tickets. I've been around the Hawks for as long as I can remember, and this is getting ridiculous.

Mike Smith getting fired was great! Hell, we were at Johnny's Icehouse when the announcement came down, and half the people there were absolutely thrilled, but then we traded away Zhamnov and Sullivan, Zhamnov, I can see the reason, but Sullivan was their only decent scorer. He leaves Chicago and scored a hat trick his first game in Nashville.

Hawks need to trade up and get Ovenchik or whatever the mad Russian player's name is. He's stacked. They need to start pulling some moves, otherwise, all of us in Chicago better hope a billionaire comes along and offers Wirtz a damn good deal. Wirtz isn't ever going to let go of that team, what an idiot. He's losing money out the ass on the Blackhawks, why the hell keep them? Make all the fans happy, sell them to someone who cares.

This topic is now closed to further replies.
 Share
Go to topic listing

  • Recently Browsing   0 members

    • No registered users viewing this page.

  • Posts

    • Intel's next-gen desktop processors leak with a whopping number of cores

      By nvaert1986 · Posted

      Is this release set for the end of this year or for next year?
    • Windows 10 KB5063159 fixes bug that wouldn't let some Microsoft Surface devices boot

      By hellowalkman · Posted

      Windows 10 KB5063159 fixes bug that wouldn't let some Microsoft Surface devices boot by Sayan Sen Microsoft released Windows 10 Patch Tuesday updates for the month last week. The one for Windows 10 under KB5060533 / KB5060531 / KB5061010 / KB5060998 introduced a bug that would not let Surface Hub v1 devices start due to a Secure Boot validation issue. As such, Microsoft had paused the update similar to the compatibility blocks or safeguard holds it applies for major feature updates as well. This bug was uncovered after the update went live, as Microsoft later added it to the list of known issues for that update and it also put up a big notice in bold. It wrote: Earlier today, the company released an out-of-band (OOB) update to address the issue. It has been published under KB5063159 and is only being offered to Surface Hub v1 devices instead of the buggy KB5060533 Patch Tuesday one. In the description of the new OOB update, Microsoft writes: You can find the support article for KB5063159 here on Microsoft's website. It is downloaded and installed automatically but users can also manually download it from the Microsoft Update Catalog website.
    • The official Funny Pictures thread

      By Mindovermaster · Posted

      I thought I saw that one, and yeah, it was awhile ago, too..
    • Acronyms....

      By Mindovermaster · Posted

      Jumping unicorns says that I forgot you. I never grunt.
    • Microsoft can't help break Windows Outlook as even opening an email now sends it crashing

      By hellowalkman · Posted

      Microsoft can't help break Windows Outlook as even opening an email now sends it crashing by Sayan Sen It is no surprise that right now, Microsoft's priority is to move users onto the New Outlook for Windows if they haven't done so already. The company began default-deployment of the new app on fresh Microsoft 365 systems and also made switching between the New app and the classic app easier. At the same time, the company is also trying to improve the new app as it recently added yet another feature that will allow people to use the app without an internet connection, and it also blocked more file types to improve security. Perhaps as a consequence of this relentless pursuit, the classic Outlook app has become quite prone to bugs and issues in recent times as Microsoft may be losing its focus. For example, in April, the downloads for Classic Outlook broke and more recently, this month, the tech giant confirmed that a major Calendar feature upgrade has broken the app in several different ways. Microsoft has provided workarounds for several of the issues so check this article out if you are having problems. And the bugs just keep on coming as Microsoft earlier today confirmed that opening emails or starting a new email will now crash the application, and it affects all channels. The company explains: Opening a mail on an email client is probably the most common and basic functionality a user is expected to do, so it is annoying to see such a bug not getting caught during testing. Again, this perhaps indicates that Microsoft's focus maybe elsewhere at the moment. The company has shared the Windows Event Viewer Log for the crash and the problematic OLMAPI32 DLL file is related to Microsoft Messaging Application Programming Interface (MAPI). The issue reminds us of the similar OLEAUT32 dll issue fix in our recent ReactOS article. The event viewer log notes: Faulting application name: OUTLOOK.EXE, version: 16.0.14334.20090, time stamp: 0x683fe030 Faulting module name: OLMAPI32.DLL, version: 16.0.14334.20090, time stamp: 0x683ff910 Exception code: 0xc0000409 Fault offset: 0x00196e1c Faulting process id: 0x9100 Faulting application start time: 0x01dbdbe04fe54514 Faulting application path: C:\Program Files (x86)\Microsoft Office\root\Office16\OUTLOOK.EXE Faulting module path: C:\Program Files (x86)\Microsoft Office\root\Office16\OLMAPI32.DLL Thankfully, Microsoft has issued a workaround for the problem as it currently investigates the bug by manually creating a FORMS2 folder which should exist at the following address: C:\Users\\AppData\Local\Microsoft\FORMS2. Microsoft explains: You can find the support article for the issue here on Microsoft's official website.

  • Recent Achievements

    • Week One Done
      korostelev earned a badge
      Week One Done
    • Week One Done
      rozermack875 earned a badge
      Week One Done
    • Week One Done
      oneworldtechnologies earned a badge
      Week One Done
    • Veteran
      matthiew went up a rank
      Veteran
    • Enthusiast
      Motoman26 went up a rank
      Enthusiast

  • Popular Contributors

    1. 1
      +primortal
      687
    2. 2
      ATLien_0
      268
    3. 3
      Michael Scrip
      184
    4. 4
      +FloatingFatMan
      177
    5. 5
      Steven P.
      140
    Show More

  • Tell a friend

    Love Neowin? Tell a friend!