Skip to main content
/

Site Navigation

Your Account

Choose Language

A question about software guides.

So I just finished putting together this, https://www.ifixit.com/Guide/How+to+stop...

@jeffsu I want to know what you think about it, and if this would be OK for a software guide. I think it is very useful because its just generally annoying when windows installs apps automatically without permission.

If you don’t want this up, please do not delete it. just make it private.

Now, after reviewing it all, I did notice one thing: In the first photo of step 2, my IEP documents, (IEP.pdf) can be seen. personally, I don’t really care that much about it, but If you would like I can cut that part out.

Answered! View the answer I have this problem too

Is this a good question?

Score 0
Add a comment

2 Answers

Chosen Solution

@captainsnowball I agree it’s useful, and guides on iFixit have to be useful—but they also have to be repair-related, and that’s really the question. Do you feel this is repair-related?

I usually won’t delete guides that are sort of on the margin, especially if the author is an active member of the community and has made other good contributions. But, I would encourage a fairly strict standard when it comes to software guides. If it’s something you need in order to complete a hardware repair—cloning a drive, installing an OS, etc.—it definitely has a home on iFixit. If not, you may want to think about whether it would be happier somewhere else.

In an ideal world, I’d like to give you guys even more leeway than we already do, but there are armies of spammers waiting to wedge open any crack we leave in iFixit’s publishing standards. Software is a giant can of worms in that regard. So I think the general rule should be no software guides, with rare exceptions as outlined above.

Hope this helps!

Was this answer helpful?

Score 2

2 Comments:

@jeffsu And that's why I used the UPD guide as an example. There is hardware involved (my personal printer). It's useful for systems like a family member I CANNOT get the standard HP driver packages to work without a wipe and reload. I don't want to mess with an ingrained issue with multiple potential causes, not being helped it's been neglected for *years* since I don't want anything to do with it. I considered a software fix before but since I've had this issue with 2 different printers (1 with modern OS support that isn't shoehorned) it's too deep to practically fix without a reinstall. SFC/SCANNOW passed, so the cause is inconclusive.

It could also be applied the other way - If I try and use my M401n on Windows 10 (when it's my turn to upgrade systems) and like a few years ago the tools don't work right I might just throw the idea of using the M041 driver out and go to the UPD.

I chose that with them because I can either try and fix an unknown problem that's been ignored for years by me and the owner (since it's not easy to fix) OR use a workaround until I can get the green light to wipe out the system and start over. I'm using the UPD (in this case, when we finally replaced the 20k+ page count inkjet, the UPD) as a compromise since their system is affected by Meltdown/Spectre and lacks high-speed patching. Seeing as they don't need to scan (nor need the HP tools), it's a compromise we both agreed on. When they need to scan, we'll talk again and see what to do.

I explicitly warned him about the leeway I get because I wanted to keep his expectations realistic. I found out about the spam issues the hard way and had to recall the UPD guide a few times... I'm with you (and the others) on being strict about it.

by

@jeffsu I'm going to assume thats a no, and I'm gonna make it private. I'd love to help out with the spam, but I'm not exactly in a high enough position to deal with the spam in huge amounts like I usually try to do. (see 70 pages of moderation votes denied) I do see that I have started something as people are starting to take advantage of the loopholes in the rules. (https://www.ifixit.com/Guide/Windows+10+...)

along with this guide I will also pull my other guides, https://www.ifixit.com/Guide/How+to+get+... https://www.ifixit.com/Guide/How+to+upda... https://www.ifixit.com/Guide/How+to+upda...

https://www.ifixit.com/Guide/How+to+Spee...

by

Add a comment

How I approach this is I ask myself if the software solution makes sense. as @jeffsu mentioned, I base it on how useful it is. An example of one of these guides I don’t bother with is Windows installations because it’s a 10 minute procedure, nor do I integrate into guides (on purpose by the way) to avoid OS “flame wars” so my guides are OS neutral. Sorry, but a Windows guide is NOT worth my time.

However, I have done it for things like the HP UPD (just updated this) and removed the 1012 Vista reference as I only put that in while I transitioned to the UPD due to the 1012 driver being 4 versions of Windows old, hard drive diagnostics, battery calibration and such just to name a few.

While I have no hesitation with software guides, especially if it can help with hardware in some way like scoring a workhorse color laser printer at the price of a razor and blades unit from Walmart (even with 100k+ pages, especially if the engine is well built) if you’re willing to put in the time to setup the machine with alternate drivers, or tools on identifying failing hard drives or even identifying if a laptop battery has usable life left even if it’s older. However, I probably get a lot more leeway then someone who is new. FYI: The 1012 guide highlights the problem with hardware specific software guides - things change quick, and it may bite you later. It only lasted 4 years before it was on death’s door and it was a complete waste of time.

If it’s too far into the grey, I wouldn’t spend too much time developing it until you have it cleared by admin. Make it usable (and knock out the major bugs), but leave room to improve that’s intentionally planted so you can do a lot with it once it’s clear.

Was this answer helpful?

Score 1
Add a comment

Add your answer

Aiden will be eternally grateful.