Quantcast
Jump to content

  • Join Today, It's Simple and FREE!

    Register now to gain access to our webOS user support forum. Once registered and logged in, you will be able to post a user to user support request topic to this site or reply to existing topics posted by other users. You can also take part in our other webOS user forums. You'll be able to customize your profile, receive reputation points, while also communicating with other members via your own private inbox, plus much more!

Sign in to follow this  
pivotCE

[pivotCE] TIP: preware.net solutions for WOSQI, Preware v1.9.13

Recommended Posts

You may have heard that preware.org was snatched away from webOS Internals yesterday.  If not, what the heck?  You live under a rock?  I digress.

Long story short, preware.net is now the new home for all things Preware to include our beloved patches, homebrew apps, etc.  Don’t bother copying and pasting that as a link because until the ducks are lined up there won’t be much to see.  I’ve been assured that the Preware Homebrew Documentation app and get.preware.net will all be updated in the near future.  Come on.  This stuff takes some time.  Relax.

So this domain snatching business was pretty ugly.  Turns out “preware” means something very different to the folks that grabbed the domain and they have no intention of selling it back to webOS Internals which was the initial assumption.  No, in fact they plan to use it for whatever “preware” means to them.  Like you, I am waiting with bated breath for the answer to that mind boggling riddle. :|

But now that preware.net exists and more importantly, ipkg.preware.net, the home of patches, apps, etc., how do you fix your broken webOS Quick Install (WOSQI) and Preware that point to preware.org?

Fix WOSQI

You’ve got a couple options here.  Until an official version bump is released you’re going to have to settle for some workarounds.  The good news is they are relatively simple.  The bad news is you’ll have to do more than just download a file.  What?  Work?  I know.  Sorry.

UPDATE: Jason Robitaille, creator of webOS Quick Install, has merged the commits by pattyland. He has not yet answered the question as to whether we can expect an updated build on the main WOSQI thread on webOS Nation Forums, however, pattyland went ahead and built a new version of WOSQI.  It is UNOFFICIAL! You can download the .jar here.

Option #1 – Edit your computer’s hosts file

This is probably not the simplest solution but it’s a solution nonetheless.  And I’m going to give you folks the Windows answer. Mac and Linux users, I assume you already know what you’re doing. Nerds. ;)

Hit the Windows key on your keyboard.  start_keyboard_windows_key

notepadType notepad.  Don’t open Notepad, right click on it and click Run as administrator.  Click yes on the box that appears or type in your admin password and hit yes.

 

hosts
In notepad, click File > Open and browse to C:/windows/system32/drivers/etc/. Change Text Documents (*.txt) to All Files (*.*).  Then click hosts and open.

 

edithostsAdd 140.211.169.161 ipkg.preware.org like you see in the screenshot. Click File > Save and then close Notepad.  Now open WOSQI and all should be swell.
Note: If you go this route, you’ll have to do it for every computer you use WOSQI on.  You could also edit the hosts file on your webOS device(s) too found in /etc/hosts BUT same deal, every device and it does not survive a doctor.

Option #2 – Replace PackageFeed.class in WOSQI .jar

I thought I would go into a step by step detail about how to modify PackageFeed.class inside WOSQI’s .jar file here but instead I modified it for you and all you have to do is drop the file in place.  Get the file from here, open the PackageFeed.zip, and extract the PacakgeFeed.class file to your Desktop.  And then do this:

1. Get 7zip and install it. Run the .exe or the .msi and “next next next finish” yourself until it’s done. You can also use whatever compression tool you like.
2. Find where you store WebOSQuickInstall-4.5.0.jar on your computer. Right click on it and choose 7-Zip > Open archive or Open with > 7-Zip File Manager

3. Navigate to .cacanucksoftwareipkg (see image). Find the PackageFeed.class file you downloaded and drag it into the 7-Zip window and click Yes when it asks you if you want to copy files to the archive.
4. Close 7-Zip and open WOSQI.  Ta-da!

UPDATE: I removed Option #2 for the WOSQI fix because for whatever reason I could not get the fix to duplicate on another computer.  Also, a couple nice folks pointed out their frustration with the fix since they couldn’t get it to work either. Must have been a fluke.  The good news is, the correct changes have been made to the WOSQI github but will have to be accepted first. Hopefully, Mr. Jason Robitaille builds the updated WOSQI and adds it here

Preware

Preware’s version was bumped yesterday to 1.9.13.  It fixes the .org problem and also the birthday icon which never got updated after last year’s Preware birthday.  Anyway, to get Preware going again you have a few options.

Option #1 – If you jumped down here because fixing WOSQI seemed annoying…well, you can skip to here but IF you fix WOSQI first all you have to do to get the updated Preware that fixes all the old .org feeds to the new .net ones is click the globe, search for Preware, and install it.

Option #2 – Uninstall Preware on your webOS device first.  On your PC grab the .ipk here, plug your phone or TouchPad into your PC, open your broken WOSQI, drag the .ipk into the WOSQI window and click Install. Done. Now scroll up and fix WOSQI.

Option #3 – On your webOS device copy this URL http://ipkg.preware.net/feeds/webos-internals/armv7/org.webosinternals.preware_1.9.13_arm.ipk, open Preware, immediately swipe down for the menu and tap Install Package, paste the copied URL into the File box and click Install. Preware will close. Reopen it and you’re good to go.

Note: When I first fixed Preware I had old beta feeds added and some of them didn’t auto-update to the .net address.  To remedy the situation I uninstalled the new Preware, removed the beta feeds, readded the beta feeds, and reinstalled Preware.  Problem solved.

Well there you have it. Good luck!

#webosforever



View the full article from pivotCE

Share this post


Link to post
Share on other sites


Sign in to follow this  



×