“The Digg Effect”

You all know the “Axe Effect,” right? I think someone needs to make a commercial out of the “Digg Effect.”
My god!!! Servers are taking a severe hit right now, they go offline for 5 minutes at a time as the backend goes down.

As soon as the load starts to settle for the hour (before my next article goes up :P) I’m going to optimize the MySQL Database, run a couple of queries to clean it up and stuff.. I’m backing it up nightly as well, don’t know when this host will give!
Anyway, yeah, if traffic keeps like this, I know a good host. If you have any suggestions, I could do with all the help I can get!

Making XP work with Apple’s EFI

Macintel Articles @ NeoSmart:

What’s wrong with us!? With me? Windows was my first OS, yet it never crossed my mind to modify Windows to work on EFI? Instead I’ve been taking the super-long, weary, and winding road of getting an iMac to become BIOS compatible. Well, I’m back on familiar terrain, modding XP is where I think I can make it work. Instead of using BIOS emulators or chain-bootloaders and what not, how about just making XP run on EFI? What is NTLDR??

To put it real simple, the NTLDR is activated by the BIOS in order to boot an NT-based OS. NT based OSes include Windows XP, our current focus. NTLDR requires a bootsector in the MBR. EFI requires that a null MBR exist, so using fixntfs as highlighted in my previous post activates the MBR, and allows the booting of XP. After you activate NTLDR, ntdetect.com is run, which gathers hardware information and creates the low-level hardware information layer, which in turn is where Windows XP sends its BIOS-related commands! From Wikipedia:

NTLDR runs ntdetect.com, which gathers information about the computer’s hardware (if ntdetect hangs during hardware detection there is a debug version called ntdetect.chk which can be found on Microsoft support […] Starts ntoskrnl.exe, passing to it the information returned by ntdetect.com.

Continue reading

Hardware Hacks: Macintel XP

Macintel Articles @ NeoSmart:

What started off as a simple post with my ponderings has kicked off quite a stir and now I am deeply motivated to find a fix.. Call it OCD, call it perfectionism, call it (uber)geekiness, I need to find out what can be done to make it work….

Hardware Background

What I am trying to do here is to find a way to do this short of adding another motherboard to the box. Obviously a cheap hardware solution is better than an extremely time consuming software fix, which is still better than buying another mobo just for Windows :) OK.. First let’s establish some facts on the mobo used in the MacBook Pro and the iMac Core Duo (sorry about the naming confusion earlier guys!).

  1. Intel makes the chips. 100% of them. Nothing on it is made by Mac. Maybe programmed by Mac, but not made by Mac. Why? The only reason they switched to Intel was because the cost of making anything compared to Apple’s share of the market nowhere near justified the price. So Apple uses boards made by Intel. Not even customized Intel boards, because that was their gripe with IBM. Apple just doesn’t have enough demand for them to give them customized chips. Also Intel stated that the boards for Apple were just like any other board.
  2. EFI. Currently the biggest obstacle. Intel stated it uses standard boards for Apple (see point 1). From what I have managed to gather the only Intel board with EFI support is the 945 chipset. Not even the 955 or 975 has EFI support. All 945 chipsets currently sold to the public (besides Apple obviously) use BIOS, not EFI. Now that is something interesting to take note of!
  3. The rest of the hardware is one hundred percent PC (ergo, Windows) compatible.

So VERY simply from what I have been able to determine… Mac programmed the EFI and flashed it to a EPROM/Chip on a mobo that supports EFI and/or BIOS. The solution to booting XP on a Macintel is one step:

  1. Grab the BIOS chip from a 945 motherboard and replace the EFI Chip on the 945 in the iMac with it…

But, there are obviously (immediately visible) issues.

  1. It’s an original Intel mobo, not a rebranded (like Chaintech or Abit) so it should technically work….
  2. But at the same time it is a desktop chip which means you lose the APM (advanced power management) features for a Mac.. Or do you?
  3. Well, even assuming it works and you get BIOS onto that mobo of yours (no mean task by itself); congratulations you now have a PC. Not a Macintel. A PC!!!!

Obviously that is not what we want…. But then there is more that can be done to make it work… Now I *presume* OS X won’t boot on a non-EFI platform.. But I highly doubt that Apple would be so naive as to use security via obscurity. After all, soon enough EFI is coming to the PC world too (hurry up Dell!). I believe the key to stopping people from using Macintosh on a PC is the TPM chips encrypted with Apple’s private key. But nevertheless, it boils down to one question: When they compiled the BSD kernel for Mac OS X for Macintel, did they just add EFI support or actually go back and strip out BIOS commands?

Logic would say that they only added EFI and not removed BIOS, simply for compatibility reasons; and should they ever want a BIOS Macintel, they have the compatible code already. What’s more, to actually remove BIOS support from the BSD kernel is like finding needle splinters in a haystack. So long as the code is in an IF bracket that is only activated if BIOS=true it doesn’t slow done the operating system any. So assuming the above is true, you should be able to boot Mac OS X on a BIOS’d version of an iMac or MacBook. Now what if it isn’t true? This is a “guaranteed to work & much work required solution.”

  1. Get a blank EPROM BIOS/EFI chip.. Or just wipe an existing 945 chip clear.
  2. Use asm to write a very simple menu where upon boot you are asked to select EFI or BIOS.
  3. Copy the original EFI code and the legacy BIOS code to the chip. They should fit, it’s a 4MB chip.
  4. Upon selecting EFI or BIOS you get forwarded to the respective code.

Now where to find someone that knows asm that well? Intel, AMD, Apple, Soyo, Award, or AMI would be my guess, but why should they make it anyway? Yeah, so the above was how to do a hardware base solution for XP on Macintel. Why a Hardware Solution is Best

  1. You don’t mess with HD images to get XP installed.. You just get the BIOS working then install from CD
  2. Minimal trouble for the final user… Just get a chip, replace, and boot.
  3. Most likely to work and “failproof”

Why NOT a Hardware Solution

  1. End users will have to buy a chip.. And as far as I know, they are hard to get.
  2. Takes the most time to get working, and most amount of “Hackers’ R&D”
  3. Immediate compatibility with any BIOS based programs.

Actually, so long as Mac OS X runs on BIOS as well as EFI it’s quite easy to implement… If it doesn’t.. Well I told you what needs to be done, the problem is implementing it.

Windows XP on Mac?

This solution is outdated. Use EasyBCD instead.

Macintel Articles @ NeoSmart:

The Problems

  • Macintosh uses a different MBR
  • MacBooks use EFI, XP x86 uses BIOS
  • The modified Darwin Bootloader is made for EFI w/ EFI supporting operating systems

OK… So step by step. Where is the BIOS used? For what? How? The OS sends low-level calls to the BIOS that tell it exactly how to deal with the hardware. Now I don’t have the Windows XP source code at hand.. so all I can tell you for a fact is that NTLDR uses it to access the drive at first to boot Windows, and Windows uses it at *least* once more when it is mounting the drives.

The Required Programs and Stuff

  • Acronis Disk Director Bootable CD
  • Acronis True Image
  • Another computer with a clean install of XP. No programs installed at all.
  • A MacBook obviously!
  • A Windows Vista DVD (not for installation purposes!)
  • Vista boot files
  • bcdedit.exe
  • BCDedit restore file

Most of the problems can be theoretically quickly dealt with.

  1. Using the Bootable Acronis Disk Director CD on the MacBook, shrink the Mac partition. Create a new partition of type NTFS/HPFS in the remaining space.
  2. Setup a clean version of XP on a PC.
  3. Extract Boot.7z to the root drive of your XP installation.. So you have C:\Boot\
  4. Copy bcdedit.exe to the root drive of your XP installation. C:\BCDedit.exe
  5. Copy MacBook.bcd to the root drive of your XP installation
  6. Use sysprep to “reseal” your XP install and remove all hardware info from the setup
  7. Use Acronis TrueImage CD to make an image of your XP install.
  8. Use the bootable Acronis True Image CD to recreate the image on the partition you just made on your MacBook.
  9. Use the Bootable Vista DVD to boot on the MacBook.
  10. Select “Repair Startup” -> Next -> CMD -> Run too.
  11. Browse to drive C:\Boot (which is the partition you created on the MacBook and then extracted the Acronis TrueImage file to). (cd C:\boot)
  12. Run “fixntfs.exe -lh” without the quotes
  13. Browse back to drive C:\ (cd \)
  14. Run “bcdedit.exe /import MacBook.bcd” without the quotes
  15. Eject the CD and restart.
  16. In Mac now, hack the Darwin Bootloader to add another entry that chainloads Drive(0) Partition(2). With GRUB it would look something like this… I’m not sure if Darwin is the same, but this step is very simple, and has nothing to do with EFI.

    title Windows XP rootnoverify (hd0,1) chainloader +1
  17. Restart
  18. By selecting “Windows XP” on the Darwin Bootloader you should be chainloaded to the Vista bootloader, which should in turn boot the entry “NeoSmart Windows XP”
  19. If everything has gone well, XP will boot!!

TV Episode Web Calendar

I just wanted to blog this site before I lost the link again.. It’s an amazing website, looks cool, has a lot of info, and is essential to any TV Show addict. Doesn’t make a difference if you want to keep track of 24, LOST, Desperate Housewives, or The Nature Channel. http://www.pogdesign.co.uk/cat/ It’s a great site, complete with summary’s taken from TV.com

Solution for GetHwIdDrivers.exe

I’ve received many emails from people who cannot get it to run…

For anyone still having trouble running GetHwIdDrivers.exe (from the official MS Beta for Vista) from the command prompt, and cannot even get the batch files to run, then you should use this exe. It’s a GUI that anyone should be able to use, no problem.

  1. Put GetDrivers.exe in the same directory as GetHwIdDrivers.exe
  2. Run it
  3. Type a name to use for the xml file to be generated
  4. Press OK
  5. Your Done!

http://neosmart.net/downloads/GetDrivers.exe (32 kb)

Hope it helps.. You need .NET 2.0, you shouldn’t need anything extra to run it on Vista…

Apple pwned!

iPhoto comes with a new syndication style, kind of like PodCasting and RSS feeds for blogs.. But the Photocasting feature in Apple’s updated iPhoto application violates numerous internet standards, according to several dignitaries from the RSS community.

But that is not all.. They are clearly boiling, raging mad.

Apple:

Apple chief executive Steve Jobs claimed at the unveiling of the application last week that the feature adheres to the RSS standard:

“We use industry standard RSS so that anyone can subscribe. You do not even need a Mac,”

RSS Commuity:

“iPhoto 6 does not understand the first thing about HTTP, the first thing about XML, or the first thing about RSS.

“It ignores features of HTTP that Netscape 4 supported in 1996, and mis-implements features of XML that Microsoft got right in 1997. It ignores 95 per cent of RSS and Atom and gets most of the remaining five per cent wrong.”

RSS Creator Dave Winer:

“It’s pretty bad. There are lots of errors, the date formats are wrong, and there are elements that are not in RSS that are not in a namespace,”

All I can say is pwned… And stop lying.

Bush Outlaws Anonymous Online Posting

Office RichardonIf you ever doubted that Bush was letting his quest for power take control of his position, here is your chance to rant. The internet, a long-sanctified refuge for people to do and act as they please under cover of pseudonym or nicknames has lost its shield of privacy. A new law signed by George W. Bush requires that anyone that "annoys" someone online must divulge his or her real name.. The problem is, different people get annoyed in different ways.

If I say I like Barney, one of the 100k members on a forum must get annoyed at that, it?s a statistical fact. If I say I hate Barney, another person (probably more) will also be annoyed that I said that.

If I even said ‘The sky is blue,’ a psychologically challenged person might feel offended that I overstated the obvious, and if I neglected to mention the color of the sky, someone might just take that the wrong way and I’ll find myself in jail.

Why?

According CNet:

"Last Thursday, President Bush signed into law a prohibition on posting annoying Web messages or sending annoying e-mail messages without disclosing your true identity. In other words, it’s OK to flame someone on a mailing list or in a blog as long as you do it under your real name. Thank Congress for small favors, I guess. This ridiculous prohibition, which would likely imperil much of Usenet, is buried in the so-called Violence against Women and Department of Justice Reauthorization Act. Criminal penalties include stiff fines and two years in prison."

I’m going to make my stance clear: I am not under any circumstances required to give my name out. I’m CG, maybe if I feel like it I’ll tell you my name, but you know what? Ban me, I’m saying what I please under the First Amendment on any forum or blog I choose. Do what you like, see if I care.

Web2Messenger Invites…

My good friend Kristan over at digitalfive is giving away Web2Messenger invites.. I personally would never use that, rather just post my IM address in my sig on forums and such, but that is just me..

Interested? Here is the link.

Apple Insults Intel’s ‘Other’ Customers…

In under three days, Apple decides that it is the new Intel money-maker, and that it has come to do Intel a favor, instead of vie versa… Apple

Apple's television ads for its new Macs boast that for years, Intel's chips have been "trapped inside PCs–dull little boxes, dutifully performing dull little tasks." Now, the voiceover proclaims, the Intel processor will finally be set free. Of course, that's not exactly the way Intel would put it. "Never would we characterize our customers that way," Intel Vice President Deborah Conrad said in an interview. Conrad said that Intel cooperated with Apple for some particulars of the TV spot, but added, "We didn't know what the end result was going to be." The company did get a peek at the ad before Tuesday's keynote, but it wasn't too much earlier. "It's probably a good thing that we didn't see them earlier," Conrad said. That said, if Intel's work with Apple inspires some PC makers to think more creatively, Intel wouldn't complain. "We certainly hope that this innovation engine kind of picks up and that you do see the beige box makers going, 'You know, maybe we could do something that looks and feels like that.' That would be a good thing, I think, from our perspective."

CNet News Story