dencorso

That surely is a fact: people who'll gladly spend up to US$15 on an old Promise SATA add-on board won't part with US$11 for RLoew's SATA patch, a software-only solution for the same issue... for me, it's hard to understand why, but I've seen it happen so many times, I'm conviced it's a fact.

Gone? What do you mean by "gone"? It never went anywhere! It's here!

Er... "Continuous innovation", maybe?

OK. So you're now seeing it behave just as it is behaving for myself. I see the "REQUIRED", too... but, then again, it's harmless: better not try to fix what is working, you know!

Check again. It ought to be working now...

monroe seems to be the case: member badge and the donnor "$" ??? look:

There are plenty drivers for USB 3.0 that work OK on XP. But that's the wrong question: there wasn't and there still isn't any driver for *Intel* USB 3.0 on XP. And since *a lot* of machines are notebooks/netbooks/tablets with Intel chipsets, all one can do is use their ports as USB 2.0. Nothing changed, AFAIK, I'm sorry o say. But problem is not USB 3.0... problem is Intel dropping XP.

Yes. Edit must be made to work again. Great workaround, btw! You rock! xper is looking on the -X- case... his profile should be recovered sometime this week. Can you contact him (perhaps at RyanVM's or elsewhere)? If so, please tell him what happened was unintended collateral damage of the board software update. IPS has great programs, you know: they've deprecated BBCode (coz it's not cool anymore) and now not even Edit works! Is it great ot what?

Congratulations! The site is working beautifully again! BTW: Are you in good health again? Hope so! Also, since I'm talking about health, do you have any news about WildBill? He's been silent for so long and wasn't very well the last time I heard about him... hope he too got better.

You've got a point there. Well... next idea is "find a modded BIOS", which is much easier said than done, and eve then...

Did you try gparted live disk?

Well your HP Model Number is K5C53PA#ABG and you are on BIOS v. F.05... you could try updating to F.06 or F.14 ... of course, it always is risky to update the BIOS, so don't do it just because I suggested: if you decide to do it, do it because you are convinced it's worthy trying it, OK?

Yes. But it includes the thread_id, too. It's exactly the format I've quoted to submix8c, above.

Yes, direct links to posts seem to have been deprecated "by design". And that's horrible, because one has to find out the thread the post is in, to be able to use the current accepted form (quoted below). So, yes, it *IS* a big PITA. But I, for one, have been unable to find an altenative form of links direct to posts that still actually works. http://www.msfn.org/board/?app=core&module=system&controller=content&do=find&content_class=forums_Topic&content_id=114895&content_commentid=1123018 And yes, I know the "Edit" command is not working anymore! xper is working to get it back to work...

Then do a serious spelunking into the BIOS configuration. It may give you an option to make the eMMc "Fixed" "Local" "Non-Removable" or whatever. Once you get it to be seen as "Fixed", 7 will just install on it. 7 doesn't like being installed on "Removable Media".

No MS software is "abandonware".

It'd be against both MS's EoL and non-redistribution in mangled form policies, and the AV would be facing a lawsuit already! It cannot be. So, the only permissible conclusion is that whatever that someone you were talking to got in the hookah, it's pretty strong, for sure!

@heinoganda: With all due respect: keep looking for ways to port the "Primetime Content Decryption Module" to Pale Moon for Atom/XP. That has future and we know for sure it will support XP for a long time. Let Slimjet's developers fix it themselves.

Can you access BIOS?

Hi, Flasche! Long time no see! Relax, the solution has been found already (as you'd know, if you'd actually read some more of this thread... but, then again, who does?)

It's possible that Norton 9 left some ID data in one of the unused sectors preceding the 1st partition, but after the MBR, if it is a MBR partitioned disk... Symantec Ghost likes to do it to this day... Look at LBA62: if 0x7C0E and 0x7C0F are "gh", there you have it.

With RLoew's patches, and his superb support, I'm sure you can get it working...

I agree word-by-word with LoneCrusader. @pionner: if you don't have any constructive suggestion to add, then don't.

+1