Duplicate Guides (July - December)

If you’re sure about it, I can get it done.

@nick I am absolutely sure! Thanks @nick

@oldturkey03 it’s done.

@nick AWESOME! Thank you @nick

@oldturkey03 I may have to rethink how I sometimes do things for old guides at some point. My "leave it be indefinitely" approach is probably fine 95% of the time because most of the guides I am no longer working with are in a good state; I'm just not keeping up with it anymore (but I have an unwritten rule I am open to revising things if it's horribly broken; it's just not guaranteed like I fully maintain it). It's the horribly broken or pointless 5% I need to reconsider. I've got a few I would be fine with scrapping, but I'm hesitant; I consider it THE LAST option.

Other times I have "reworked" it into a more universal guide; an example of this was when I went from the LJ 1012 post XP driver to the HP UPD; I retired and privated (but never deleted) the 1012 specific guide just in case. Keeping both in the case of the 1012 driver guide didn't make sense because it just added redundancy. For retirements like the 7/8.x Xbox receiver guide, I did that because I felt better "stopping the bleeding" before something went wrong I can't fix.

Looks to be an EDU thing; they tend to look different. Schools can be quite happy to require excessive documentation that is quite redundant, even if it exists. I'll take a look.

@krisrodriguez it looks like the "Sweeper" version is cloned from the "Brush" guide; both are from the same author. It looks like one could merge them into one Wiki to me. Is that seem like a good idea?

@nick that is actually a Wiki made by the iFixit Vulcan Team. not an EDU issue :-) Agreed on the duplication.

@oldturkey03 Ah. I was going off of past experience with their work. Some of them are REALLY hard to spot quickly. I vote delete the one with the least history and merge the name, especially since there's no EDU red tape. Something like "Sweeper brush".

The reason I suspected student is because of how "rigid" it was; for example, I can decide to skip something because I do not think it will matter much, or touch something risky like monitor capacitor replacement or how to change the flash module in a camera, for instance; that may be too much of a liability for a school.

@hainzy, @oldturkey03 and @nick, thank you for catching this. Let me talk it over with the team to see how we want to proceed.

@krisrodriguez Thanks! At the moment it seems, that both are deleted or unavailable?

Thank you @sedorr, all taken care of :)

Fixed and bridged the information between the two Wikis. It was the same author, so I merged it.

@Nick, thank you so much for taking care of these.

Two different guides. 150065 is user written (2022), 160497 is written by an iFixit staff member (@mhaeussermann).

This is somewhat common when the user guide is of lower quality, neglected, or they want to ensure edit consistency since user guides may follow an exotic process that someone like me doesn't follow for whatever reason or another (ex: If I am working on a photo studio setup "guide" I could very well choose to leave out instructions on how to tape posterboard together and how to cut up the Amazon box my light stands came in and assume the reader can do 1+1=2, but iFixit may choose to show HOW).

@nick, thank you for responding :) I agree with @Nick.

But, I'll connect internally with @mhaeussermann to see how we can reduce confusion.

@krisrodriguez I wouldn't say I see this a lot. What usually happens when you see this is the staff got a copy and the user version was so miserably bad they just made their own version with their copy of the device.

I've done it too. If I do not want to deal with the old broken guide I will simply redo it my way. A lot of the time it's more work and hassle to rehab the broken user generated guide. You've seen how bad some of the guides I've given up are right? Why would I fix that unless I was absolutely willing to do it right? I'd rather hand off the torch and take the hit on losing it. There's a point where it's so bad you just do a freaking redo or let someone else have at it and make their own.

I think some of it is people do not get that these guides need to be checked once in a while. You can't finish it, let it sit and make it impossible to fix or pull tricks to maintain ownership by making it such a pain to fix it never happens. I've done that too and those guides suffer from age rot. Their time has past and it's no longer worth trying to setup proper prereqs.

@sedorr, if you come across the link for Coffee_Maker please send it over. I wasn't able to locate it.

@nick, thanks for the heads up! The screenshots look good to me.

@krisrodriguez Yeah I'd need to get the M401 out again lol. I went to a newer unit and it's not an HP. It took me a minute to patch in but it's also a low use guide so it wasn't exactly a priority, but I knew it had to be done. If Microsoft removes the legacy control panel from W11, I may need to patch the guide again to show how to setup God Mode as a workaround.

@krisrodriguez One additional amendment: On the legacy control panel, I added a note (and link) to use God Mode should Microsoft ever pull the control panel and someone has an old unit that cannot be set up without the manual method. Right now, it's more of a note than anything else, but it will come into play if they retire the legacy control panel and someone has issues with DOT4 hardware. I consider it futureproofing but I can pull the reference until it's more crucial if it looks out of place (or properly patch it in). At this point, I added it as a way to prepare if Microsoft pulls the option from Win11 in Control Panel. I can always add the Control Panel method as the backup contingency plan.

I also added an extra note to help with finding out which driver to use.

@nick, I think it's good to include it. Doesn't seem out of place because the goal is to help people prepare just in case. So my vote is to leave it as is until if/when you decide that you want to incorporate it differently down the road. But, including the information somewhere is better than not mentioning it at all. Thanks for looking out.

@krisrodriguez Right now it's more of a insurance placeholder until we see issues or changes to the legacy Control panel, not really the main method. It's so I have groundwork to better implement it if I have to later on. On one hand the information is available now should it be needed later but it also buys me time to properly implement it as native information should it become necessary.

@nick, thank you. I've gone ahead and made it private.

@knipwim, thank you! All taken care of.

@knipwim, all taken care of.