Stoic Joker

  • Content count

  • Joined

  • Last visited

Community Reputation

0 Neutral

About Stoic Joker

  • Rank
    I Hate Titles
  • Birthday 01/19/1965

Contact Methods

  • Website URL

Profile Information

  • OS
    Windows 7 x64
  1. Why not just send a WM_KEYDOWN message specifying the Win key to the shell?
  2. I've run into this three times where the cause ended up being a malfunctioning multi-media keyboard (1 wired & 2 wireless). If your keyboard has a sleep button, try changing the keyboard. Obviously there are other possible causes, but this is worth checking (if applicable). The first time I'd spent months trying to trouble shoot an intermittent issue for a client before finding out it was the blasted keyboard.
  3. Remember the 3 F's of Engineering Form Follows Function Nobody cares how pretty it is, if it don't work.
  4. (The entire header looks bogus) It's one of many typical spammer tricks designed to candlelight some one into doing something detrimental - Either over tweak and ruin their spam filtration software, or just confirm their address is valid so the game can go to the next level. If you've eliminated the obvious, the best thing to do is nothing.
  5. Point taken... and considering I owned a bar for 3 years (confirm-ably) quite true. However, when faced with actual facts (like on a test) most (pontificating) know-it-alls crumble rather quickly.
  6. Okay, so while I'm not in the mood to play with image hosting...I did take the test. Two thing I feel are relevant to the results: I did not make any attempt to cheat & I am currently legally drunk... Score: 102
  7. (5ms) Might seem like enough time, but it ain't ... especially if the device you're pinging has a sleep mode (like a printer). I've seen them take up to 150ms to answer the first ping (depending on how soundly they were "sleeping"). Mind you I only have the snippet posted to try to grasp the intent with. But a typical ping would go: Name Lookup ping ping ping ping It appears you are going: Lookup ping Lookup ping Lookup ping Lookup ping Which granted would make the standard 3sec timeout rather annoying as you loop past it four time. I generally only code in pure Win32 API C++ so I usually just use gethostbyname(pstrHost); which I've never had a problem with. If you are trying to force your way past a standard protocol timeout, you're pretty much asking for trouble. Better would be to rethink the overall approach. May multi thread at a higher point so multiple targets can timeout simultaneously.
  8. 5ms is no where near enough time to (reliably) do name lookups. Why are you doing it repeatedly? Even if the response times were ideal, it's still going to badly skew your ping times. Do it once, then pass the result to the ping code. ...Then the 2sec you should wait for a reliable answer won't be such a big deal. Just a Thought Stoic Joker
  9. Well, if you like troubleshooting Mac stuff, and can't figure it out either ... at least I can feel better about having the issue unresolved. Thanks
  10. I tempted to lean that way also, but I still suspect a spooling issue based on how the data is being sent to the printer (burst pause burst pause (for half an hour)) I work for an HP Authorized Service Provided - They're really just slow with releasing updates ...But HP's site (still) says to use the driver included with SL (which we did). Not that I'm aware of. The thing I find most troubling in this regard is the existence of several post on the Apple's support form which reference both Snow Leopard & slow network printing with devices from a variety of different manufacturers. There are a few Poke-and-hope (try this) solutions, but... The only consensus that I've found resolution wise is that Apple is working on it. If it was beating on the processor and not getting to the spooler I'd go for the driver explanation. But it hits the spooler (print queue) just fine, which kind of implies the driver (pagination) is done with it.
  11. Greetings, and thanks for popping in. Let me clarify a few things, the first being... there are no Windows machines on this network (That's why I'm lost ). User in question is a sixty-ish photographer/blogger/Apple zealot. So there are only the two Snow Leopard laptops an AipPort, and the printer (with Bonjour enabled/running) as contenders on the wire. He's also not prone to "tinker" with the machine so what ever the defaults are is a safe assumption. Yes you are correct is assuming that this is a direct IP (e.g. not shared) configuration. Both Laptops are OSX 10.6.2 (which both behave the same (badly)) ... So I got no shot at a tie breaker. (Ah! Just remembered...) Both machines were upgraded to SL shortly after it came out (guy likes to stay current) both machines printed fine to an HP LaserJet 3000 before and after the upgrade Now, I'm assuming the SL upgrade did not also update the preexisting printer driver, but the newly add printer (printers actually - this is the third one he's tried) getting the new driver are dieing (performance wise) as a result. (Mind you, I'm just trying to piece together what I've Googled to create a "picture" to work from here)
  12. Greetings a customer bought a refurbished HP Color LaserJet 3800n from the company I work for. It has been throughly checked out & performs flawlessly on a Windows network... However. The customer has an Apple AirPort WiFi network with two OSX 10.6.2 (Snow Leopard) laptops. Being a "network" install, I got roped into doing the setup. Fortunately, I've been futzing with Linux quite a bit here lately so I wasn't completely lost on the install (I used the HP JetDirect/socket option, which both Apple & HP support pages state is the correct option). The printer works, sending a Word document, in a reasonably normal period of time. But. Trying to send a picture (1.4MB .jpg) from Adobe PhotoShop (or the Mac picture viewer) takes roughly half an hour (this is not an exaggeration). My Win7 machine at the office will print the same image to the same printer in 15 seconds. I'm guessing at this point this is an Apple issue - Googling brings up several (hundred) hits that also imply that this is the case. However there is absolutely no consensus on what the cause/solution might be. ...And I'm not real comfortable just having-a-go at the machine for fear of screwing it up. So, does anyone have any (preferably first hand but I'll take what I can get...) insight into what may be going on? I'm reasonably sure that it is not a network performance issue, and (at this point) that the problem lies with the Mac. What I don't know is what (if anything) can be done about it. Side Note: When the customer connected the printer to their Mac via USB it printed fine (which I'm guessing gets Adobe off the hook). It is only the network printing performance that is suffering (horribly...). However being that this is a laptop, a USB connection is not an acceptable permanent solution.
  13. Greetings This has been driving me nuts for months... We have a client that is using Cisco's ATA 186 (Analog Telephone Adapters) VoIP devices. The devices are working fine with other fax machines and a plain telephone that I'd brought for testing purposes (Just to satisfy my own curiosity). The issue that is being had is with an HP LaserJet M5035 MFP (Multi-Function Printer) that uses an on-board Q3701A fax module. The issue is that while the HP can both consistently & successfully send faxes through the Cisco box, it can not receive faxes. More specifically it will not respond to the ring tone generated by the Cisco box by opening the line and checking for a carrier signal which would tell it to get the faxing show on the road. This can be confirmed by dialing the devices line number from either a phone or another fax machine; the line will continue ringing until the TELCO breaks in and plays the hay dummy there's nobody there message. This (IMO) is caused by HP's much (over) hyped built in Distinctive Ring functionality, which (allegedly) allows infinite configurability...with one glaring exception, you can not shut it off. It is my understanding (after extensive testing) that this particular option is crucial, given that it has been successfully used to resolve this very issue, in this very location, with fax devices made by other manufactures who had the foresight to afford their clients the option to configure the device to just answer the blasted phone instead of insisting on IT personnel having to play this guess-the-magic-tone game. My hope is that someone here has encountered this issue and discovered a resolution that they are willing to share, as HP's "Tech Support" has been completely useless in this regard.
  14. Hay, at 43 I've had plenty of time to forget most of that stuff ... so I was happy with the 73% C that I got.
  15. Ya know it seems like 90% of the people that have trouble with an AD domain created the problem themselves by mis-configuring DNS. The most common error is putting your ISP's DNS servers in the workstation network configuration. Being that your ISP knows nothing about the completely unregistered private internal domain both the DNS lookup and the domain join operation fail together. The other classic boo-boo is putting the ISP's DNS servers in the Domain Controller's network config, which simply results in a DC that can't find it's own a**. DHCP (if used) fails shortly there after and the fun ensues. In a single server domain ALL workstations point to (and ONLY to) the Domain Controller. The DC Uses itself (and ONLY itself) to resolve DNS. If you want to configure DNS forwarding for external names open the DNS management console (dnsmgmt.msc), select properties of your DNS server, and add them to the forwarders tab there (and there only). If you don't add forwards server 2k3/2k8 will both default to the internet root servers alowing you to still "get to the web". The key is making sure the server can identify itself, because if it doesn't know "who" it is it can't identify everybody else either...