I have just changed the lupu_520 to lazy_528. Only removing spaces came to success.

Don't know why...

However, i did it two times and the second time i did it running the first created and installed puppy setup.

This your work is really fantastic and it makes the whole thing i am working on for about the last six months going perfect. It offers me new ways to provide puppy in a (imho) very special way and maybe turning some vegetables back into human.

Thanks so much Shinobar for the quickset wary511 windows installer. I installed it on my Acer Travelmate notebook(from 2002) WinXP OS and everything works fine;merely changed the screen resolution to 1024x768,updated SeaMonkey to ver 2.5,etc. That was two days' ago. Today,I installed the gtk 2.28 lib file (because Seamonkey 2.5 requires at least 2.20 or higher,etc) and rebooted the PC to try another distro and saw this message :...Terminated. #Journal commit I/O error. Later when I try to get back into Wary 511,my screen was almost blank, i.e. xserver (vesa) was garbled. I tried xorgwizard a few times but to no avail. Any help appreciated.
Btw,is it recommended that I upgrade it to Wary 522 by copying the necessary files to the same subfolder? If not advisable,it's ok as it has worked well for me so far and I've tested Wary 522 and the touchpad mouse pointer would hang for no reason sometimes.
I think my pupsave file is damaged,so I booted into WinXP to delete it,then reboot into Wary511 ram mode and created a new pupsave;now it's working alright. Btw,tested Wary522 on the same noteboot but my synaptics touchpad mouse as well as the usb mouse that I plugged in would hanged in xvesa(xorg doesn't work),so I guess I would stick with your quickset wary511 which has been running fine so far. Thanks.

Hello, my Quickset wary 511 keeps getting "journal commit I/O error" whenever I reboot or shutdown. It was installed using Windows Installer-V1.1 released on my WinXP notebook. Before,my pupsave was corrupted after installing some programs in wary 511, after which I had to delete it in windows and reboot in Wary511 RAM mode to create a new one. And now again after installing and removing a few pets and packages, the journal commit I/O error problem resurfaces but surprisingly I can still boot into Wary511. Apart from this problem, I'm very happy and thankful for Shinobar's quickset wary511 windows installer as it has been working fine on my 10-yr-old Acer travelmate TM632 notebook. Is there anything I should do or look out for? Kindly advise.

Latest: The "journal commit I/O error " disappeared after I delete the puppy.swp that I created and use swapfilemanger to build a new one.

Hi, I used the windows installer in the 1st post to set up Lucid Puppy Linux 528 but could not create a savefile upon reboot or power off, the screen simply blanked off. It didn't even asked me if I wanted to create one. Exiting to prompt also resulted in blank screen.

Slacko 5.3.1 installed and ran without a hitch. Lucid Windows Installer was the second one I tried. Both were checked for md5sums integrity to be matching.

My understanding is that the second windows installer onwards will automatically edit the menu.lst and copy the core puppy files in the created subdirectory. FYI, a full defrag in Windows was also done,it took me 3 hours.

Yes,my harddisk has a hidden recovery partition, so C: is recognised as sda2 and root is hd0,1.What went wrong? Please advise. TIA.

There is nothing wrong with the Windows Installer. You would get this with the Live CD as well.

The problem is an incompatibility between Puppy and your graphics card. This has been noted for various versions of Radeon before. A search of the forum would find other people with this problem and how some have solved it. I think running with a vesa driver may solve the problem but this is a rather drastic solution as other graphic features (prefered resolution) may not be available with vesa.

I don't have a radeon so cannot suggest a solution.

Regarding the save file. One user created a blank one manually and saved it in the same directory as the puppy sfs file. It will then be seen at start up and perform OK.

Thanks for telling me. Only managed to manually create a lupusave.3fs using the simplesave.pet.

Searched in vain for a solution to my Radeon HD5450 problem with lupu528. Used quickpet > Drivers > Test your graphics card, then downloaded the recommended ati_catalyst_10.10.lucid.pet driver but upon reboot found all the desktop icons greyed out except quickpet; even wifi failed to connect and had to be wired to do so.

This Radeon HD5450 with Puppy Linux 528 is real disappointing,frustrating, a PITA. Just my luck. The saving grace is Slacko 531 and Lighthouse Pup 503 both work fine,quite consoling.

First,thanks to ICPUG's advice to manually create savefile first, which I did courtesy of the simplesave.pet by stu90;thus bypassing the blank-screen-unable-to-create-savefile-problem.

Second, using quickpet>drivers>test your graphics card, and then accepting to download and install the recommended ati-flgrx-10.10-catalyst.lucid.pet didn't really solved my Radeon HD5450 card issue - the ati driver failed to load properly or performed with issues and all the desktop icons saved quickpet were greyed out.

Third, uninstalled the said ati 10.10 driver and used vesa.

Fourth, compiled the ati flgrx catalyst driver using the latest version 11.12 from AMD. Still the desktop icons were greyed out.

Fifth, downloaded and replaced the lupu528.sfs with the latest updated one 528.004 after having come across it on the web. Presto! the greyed icons were restored to original colourful state!

Lastly,perhaps,and on hindsight,provided I was aware of the updated lupu528.004.iso in the beginning, if I had straightaway replaced the original iso with the updated version,it might have saved me a lot of heartaches.

You cannot post new topics in this forumYou cannot reply to topics in this forumYou cannot edit your posts in this forumYou cannot delete your posts in this forumYou cannot vote in polls in this forumYou cannot attach files in this forumYou can download files in this forum