• (cs) in reply to VeeTwo
    VeeTwo:
    For the FundRaiser select (or is it "Selectis?"), I'm going to venture a guess that a 10 year old computer will typically be too old for Windows 7, and yet, we see an Aero-style dialog box. That leaves only one conclusion: TRWTF is Windows Vista! That would also explain the -119mb.

    Sorry, some of us graduated from Vista years ago.

  • (cs) in reply to It's Pat
    It's Pat:
    re: password

    And the password textbox is copy/paste restricted...

    TRWTF is that this is possible.

  • Your Name (unregistered) in reply to DCRoss
    DCRoss:
    Your Name:
    Do you have prior experience writing a web form?

    Right or wrong, that's just the way web forms were...

    Oh, forget it. I see that joke's already past its expiry date.

    Which would be okay if I was writing for an embedded system which doesn't even have an expiry... Nope, that one's dead too.

    Um.. More Irish Girl? Bring back MFD? Today is September 7290, 1993?

    Dang, I need to clean out my fridge more often.

    Irish Girl is NEVER past the expiration date. :-)

  • ideo (unregistered) in reply to VeeTwo
    VeeTwo:
    For the FundRaiser select (or is it "Selectis?"), I'm going to venture a guess that a 10 year old computer will typically be too old for Windows 7, and yet, we see an Aero-style dialog box. That leaves only one conclusion: TRWTF is Windows Vista! That would also explain the -119mb.
    Reading comprehension fail. The computer is brand-new, it's the *program* which is 10 years old.
  • BlueBearr (unregistered) in reply to Shaun Forsyth

    You're right - WinXP doesn't show the blow-by-blow info at the bottom of the screen like that during updates.

  • Butterstick (unregistered) in reply to lolwtf
    lolwtf:
    pjt33:
    The base-64 "password" decodes to 49 bytes including a number which aren't printable. As hex it's 00DED88E27741111A4155DA75800A4FF8A2422B5D9FB5C4F5E069164DF7F60FEF9FD2BDC5D35E02EC318772B681999E6AF.

    It's unlikely to be the raw password, and we can rule out bcrypt (60-char output). MD5 gives 16 bytes of output, and SHA-1 gives 20 bytes of output, so they would be using stupid amounts of salt. It seems most likely to be SHA-256 (32 bytes of output) with 16 bytes of salt and a leading 00 as a version indicator. Anyone want to try cracking it on the assumption that it's only hashed once?

    I was going to assume the password is just a string of random bytes base64-encoded.

    Actually, it looks like an Amazon AWS S3 access ID and secret key, separated by the "/". CINE BUZZ may be using S3 in some fashion for their website.

  • ¯\(°_o)/¯ I DUNNO LOL (unregistered) in reply to erk
    erk:
    The second image shows another typical WTF. It asks for the card number "without dashes or spaces". It's much easier to compare the number you've typed with the card if you leave the spaces in. But then you run up against the programmer who can detect spaces in the number, but isn't clever enough to remove them.
    I think that's more likely to be some WTF rule by the credit card companies that they won't allow you to change the entered number in ANY way, including removing blanks. I can't ever remember seeing a credit card number entry field where you CAN enter blanks.
  • (cs)

    To be fair, any program would run slowly with only -119 MB of RAM.

  • (cs) in reply to DCRoss
    DCRoss:
    Um.. More Irish Girl? Bring back MFD?

    There's 2 things I'd be happy to see ;)

  • Norman Diamond (unregistered) in reply to Shaun Forsyth
    Shaun Forsyth:
    "I submit reason number one why you should start up your old XP box every once in a while even if you don't need it...just in case you might want to use it again," writes Bobbie.

    Ummm is it just me or is this vista / windows 7, not XP WTF??

    Yes it is, and that's exactly why you're better off sticking with your old XP box.

    The following screenshot looks like XP but it was really Longhorn (before Longhorn was renamed to Vista and the folder was renamed from C:\Documents and Settings to C:\Users).

    [image]
  • Norman Diamond (unregistered) in reply to Norman Diamond
    Norman Diamond:
    Shaun Forsyth:
    "I submit reason number one why you should start up your old XP box every once in a while even if you don't need it...just in case you might want to use it again," writes Bobbie.

    Ummm is it just me or is this vista / windows 7, not XP WTF??

    Yes it is, and that's exactly why you're better off sticking with your old XP box.

    The following screenshot looks like XP but it was really Longhorn (before Longhorn was renamed to Vista and the folder was renamed from C:\Documents and Settings to C:\Users).

    [image]

    Huh. It displays when previewing and it's displaying now when writing a followup, but it's broken in normal mode.

    http://www.geocities.jp/hitotsubishi/longhorn_speed.png

    
                
  • (cs)

    Here, have a working link -> http://t0.gstatic.com/images?q=tbn:ANd9GcSsatQ7L6oxQ9UxJ--PGYiJ34p5gtPoV8xwWR24axYOMvmpN0RB

  • Norman Diamond (unregistered)
  • erk (unregistered) in reply to ¯\(°_o)/¯ I DUNNO LOL
    ¯\(°_o)/¯ I DUNNO LOL:
    erk:
    The second image shows another typical WTF. It asks for the card number "without dashes or spaces". It's much easier to compare the number you've typed with the card if you leave the spaces in. But then you run up against the programmer who can detect spaces in the number, but isn't clever enough to remove them.
    I think that's more likely to be some WTF rule by the credit card companies that they won't allow you to change the entered number in ANY way, including removing blanks. I can't ever remember seeing a credit card number entry field where you CAN enter blanks.

    There are loads of them. The most recent one I encountered was Co-op Energy (http://www.cooperativeenergy.coop). But it's really a lottery: I guess about half the time my card number is rejected for having spaces.

  • thingy (unregistered) in reply to tin
    tin:
    DCRoss:
    Um.. More Irish Girl? Bring back MFD?
    There's 2 things I'd be happy to see ;)
    Yes - and also MFD.
  • Kwpolska (unregistered) in reply to Shaun Forsyth
    Shaun Forsyth:
    "I submit reason number one why you should start up your old XP box every once in a while even if you don't need it...just in case you might want to use it again," writes Bobbie.

    Ummm is it just me or is this vista / windows 7, not XP WTF??

    That is 7 or 8. Moreover, Bobbie cut the power when it was updating at shutdown.

  • David Brooks (unregistered)

    Hm. My Windows 7 PC has -66MB of memory. I was sure I had bumped it up to 4GB.

  • base65 (unregistered) in reply to MightyM

    Not always ... one or more of the pad character (=) is appended to the end of a base64 encoded string to ensure that it is a multiple of 24 bits long. See RFC 2045.

  • hsimah (unregistered)

    That update screen looks more like Vista/7 than XP.

    Captcha: Sagaciter, he who oft quotes Homer.

  • JustSomeGuy (unregistered)

    The -119M problem is most likely a signed/unsigned issue. I remember an early version of one of the IDEs (Borland, I think) that run fine on machines with 512K or less but when you bumped it up to 640K, all of a sudden the IDE saw that as a negative number and refused to start.

    I'm STILL waiting for my free copy of the IDE for raising that bug. Though I'm not holding out much hope.

    CAPTCHA: conventio - okay guys, who the heck stole the 'n' key off my keyboard?

  • Bobbie (unregistered) in reply to The MAZZTer
    The MAZZTer:
    Shaun Forsyth:
    "I submit reason number one why you should start up your old XP box every once in a while even if you don't need it...just in case you might want to use it again," writes Bobbie.

    Ummm is it just me or is this vista / windows 7, not XP WTF??

    I believe you are correct, I had the same thought.

    It's XP with theming. I guess the update screen uses the boot screen image background.

    QJo:
    That first one appears not to be a WTF (unless of course MicroSloppy are to be considered TRWTF of all time).

    This seems to be a registry update, which happens from time to time after the usual "You have 12 updates - please do not unplug or power down your computer" (or whatever it says). Sometimes the updates do in fact require the registry to be updated, which happens when you next restart the machine. They don't take long (seconds rather than minutes).

    In this case, the full update took at least half an hour, but that may have been due to other updates queued as well; I had better things to do than watch it go through them one by one. You are right, however, that it's not really a WTF that an OS that hasn't been updated in a while will have lots of outstanding updates. (If anything, the opposite would be more concerning.) Pity that doing that needs to delay boot, though...

  • (cs)

    Maybe a Flash Player clone would be a profitable iPhone app.

  • Slapout (unregistered)

    I once wrote a program called FundRaiser. Don't remember that error though. Hope it's not from my program :-)

  • Neil (unregistered) in reply to Bobbie
    Bobbie:
    It's XP with theming. I guess the update screen uses the boot screen image background.
    XP doesn't have an update screen, instead it has three ways to install updates: 1. When shutting down, there is an option to install updates and shut down. After "Logging off" you get "Do not turn off your computer" before normal "Windows is shutting down" service is resumed. 2. Through the automatic updates icon in the notification area. This opens a fairly standard dialog window. 3. Through the Windows Update website (although this ends up opening the same dialog to actually install the updates).
  • (cs) in reply to JustSomeGuy
    JustSomeGuy:
    The -119M problem is most likely a signed/unsigned issue.

    It's fairly certainly that. The installer will be getting the amount of RAM as a signed 32 bit number. 10 years ago having more than 2GB of RAM would be almost unimaginable, so you wouldn't need more than a signed 32 bit number to hold the RAM size.

    But, if you now have an average 4GB PC with a bit of RAM used for integrated video, you'll have a small negative amount of RAM.

  • Jay (unregistered) in reply to erk
    erk:
    The second image shows another typical WTF. It asks for the card number "without dashes or spaces". It's much easier to compare the number you've typed with the card if you leave the spaces in. But then you run up against the programmer who can detect spaces in the number, but isn't clever enough to remove them.

    Ditto. If you don't want to write spaces or dashes to your db, it is really so tough to strip them out? Why, that could take almost an entire line of code. Even if the language you're using doesn't have a built-in string-replace function, surely you could write one in 10 lines or less.

    What next? Ask the user to encrypt his password himself so you don't have to write the code to do it?

  • Sven (unregistered)

    Still waiting for microsoft releasing a final version before they drop support for a certain os

Leave a comment on “Patch Friday”

Log In or post as a guest

Replying to comment #:

« Return to Article