Classic Pup 2.14X -- Updated 2 series

[ttuuxxx]

here's a early mac emulator, you need a bootdisk and roms to run it,
directions how to get this to run are located http://minivmac.sourceforge.net/doc/start.html
and
http://minivmac.sourceforge.net/doc/hardware.html#rom
unlike other emulators this one takes a bit of work to get it going.
The folder with the files is located in /usr/share/Minivmac
I made a start menu in the FUN menu

can't say I spent the time to get this going so please let me know if anyone gets it up and running.
ttuuxxx

[sc0ttman]

can't say I spent the time to get this going so please let me know if anyone gets it up and running.
ttuuxxx

I have minivMac installed in my Puppy Arcade puplet - but never got it running MAC, simply because it is so hard to find MAC images that are not illegal.

[ttuuxxx]

Here's the latest MtPAint, I changed the default icons again:), played around with the icons for about 10hrs today, lol
anyways enjoy
ttuuxxx

[PenguinPupLin]

Hi ttuuxxx, thought I might ask the master himself the following question. Being a noob who is not too familiar with how this forum works,I'd inadvertently cross-posted this topic in multiple threads and hoped to finally get it resolved here;my sincere apologies.

I created a swap file called pupswap.swp in my WinXP partition for my frugal installed Classic Pup 214X-TOP9 using a method I found in the Internet, i.e in WinXP (ntfs partition),type "fsutil flie createnew C:\pupswap.swp 528244000" (without quotes, and for 512MB size). Then in Puppy rxvt, I first "mkswap /mnt/home/pupswap.swp" successfully as it showed the correct size and UUID. But when I wanted to turn swap on by " swapon /mnt/home/pupswap.swp" , it said "swapon: argument is invalid". Upon rebooting puppy,the message about swapon invalid argument also appeared. What gives and how to correct it? Please help. By the way, I also tried using winfonts-3.4.pet to set my WinXP pagefile.sys as swap space but to no avail.
How do I get swap file to work,please?

[sheldonisaac]

(SOME SNIPPING)
Glad you are asking here.

I created a swap file called pupswap.swp in my WinXP partition for my frugal installed Classic Pup 214X-TOP9 using a method I found in the Internet, i.e in WinXP (ntfs partition),type
"fsutil flie createnew C:\pupswap.swp 528244000"
(without quotes, and for 512MB size).

How about make an ext2 or ext3 or VFAT partition, and in it make a 512MB file called pupswap.swp

[PenguinPupLin]

That would be my last resort,hopefully not, as shrinking an existing WinXP boot partition(worse still for Win Vista/7),as far as I know,using GParted,for example,is risky business,not yet foolproof. And in the worst case scenario where even fixmbr and/or fixboot fails, I'd have to use the Acer restore CDs that came with the 10-yr-old notebook and put everything back to default factory condition i.e WinXP SP1 (not SP3) and reinstall all my accumulated programs including updates and patches and software, a few of which I've lost or damaged the original disks.
If originally, as is the case nowadays for Acer,the harddisk had come with two partitions,one as boot,the other data,I would have done so for the non-boot partition and created an ext3 plus swap partition(not file) plus VFAT right from the beginning.
Otherwise,from the start,I wouldn't have used the windows installer to install quickset wary511 without modifying the mbr instead of the Puppy Universal Installer Grub4Dos method. The former method only adds a line in the boot.ini and places the grldr and menu.lst in C: and puts the puppy core files in a subdir just like a frugal install. In fact,having done that,I went on to add several other puppies manually as frugal installs, all in ntfs partition. That's my setup.

[ttuuxxx]

Here's the latests Claws Mail, I changed the default icon theme, then I compiled a wack of plugins and included them (adds 500kb compressed to the package)
-address keeper
-attachment warner
-attachment remover
-bs filter
-gtkhtml viewer
-mailbox
-Notification
-rssyl
-tnef parser
-vcalendar

I compiled it without gnutls also so it must be using ssl, any testers?
http://www.smokey01.com/ttuuxxx/2.14X/S ... 0-i386.pet
ttuuxxx

[ttuuxxx]

here's the latest Bluefish webpage code editor.
http://www.smokey01.com/ttuuxxx/2.14X/S ... 1-i386.pet
enjoy
ttuuxxx

[sc0ttman]

I compiled it without gnutls also so it must be using ssl, any testers?
http://www.smokey01.com/ttuuxxx/2.14X/S ... 0-i386.pet
ttuuxxx

May not be relevant your this thread, but I tested Claws in Akita, needed dbus and dbus-glib from wary5OLD repo, create a symlink, but then it worked fine, really nice.. Thanks for this ttuuxxx, I'm gonna repackage and add to my repo...

Cheers

[ttuuxxx]

I compiled it without gnutls also so it must be using ssl, any testers?
http://www.smokey01.com/ttuuxxx/2.14X/S ... 0-i386.pet
ttuuxxx

May not be relevant your this thread, but I tested Claws in Akita, needed dbus and dbus-glib from wary5OLD repo, create a symlink, but then it worked fine, really nice.. Thanks for this ttuuxxx, I'm gonna repackage and add to my repo...

Cheers

great good to hear
thanks for testing.
ttuuxxx

[Puppyt]

ttuuxx, your java+exec bin worked great in sc0ttman's Akita Beta6 too,
Many Thanks!
REF:http://www.murga-linux.com/puppy/viewto ... 348#545348

EDIT: 3 days later and I've realised I was remiss on not updating. Yes, the pet worked fine for a CF-card install of Akita6 on my main work machine, in that I was able to then select jar game files and have them open. But when I closed down, the pup_save borked. After repeated failed attempts to re-install the pet to the CF install on a slower machine - and this happened for other jre pets I tried - I found a string of err_hid_log (from memory) files all giving the same error codes. Strange pup_save failures also often occurred after a JRE pet installation. I'll move the discussion to his thread though and save hijacking the 2.14X one

[PenguinPupLin]

Sorry,where do I find the devx and source files for Classic Pup 214X-TOP9 which I need to compile the Nvidia96 driver?

I downloaded the devx_214X-TOP9.pet and unzipped, it turned out to be 819MB in size as shown in Xarchiver!? As for the source file,the earliest kernel I could find is 2.6.18.8.

[ttuuxxx]

Sorry,where do I find the devx and source files for Classic Pup 214X-TOP9 which I need to compile the Nvidia96 driver?

I downloaded the devx_214X-TOP9.pet and unzipped, it turned out to be 819MB in size as shown in Xarchiver!? As for the source file,the earliest kernel I could find is 2.6.18.8.

Install the devx pet, it comes complete with the kernel drivers
http://www.smokey01.com/ttuuxxx/2.14X/i ... top9.0.pet
ttuuxxx

[tempestuous]

Install the devx pet, it comes complete with the kernel drivers

Be very very careful !!
i) devx is just the compiler tools. Since you are trying to compile drivers (kernel modules) you will also need the full Puppy 2.12-2.16-compatible kernel source.

ii) apparently at some stage in the 214X-TOPxx devlopment, glibc was upgraded. This will potentially break compatibility with the original kernel and kernel modules, since 214X-TOP inherits its kernel from the original Puppy 2.14.
Thus to be truly binary-compatible with the 214X-TOP kernel you need to compile drivers using the original devx. Get it here -
http://distro.ibiblio.org/puppylinux/sf ... vx_216.sfs

Then the original, 2.12-2.16-compatible kernel sources are here -
http://distro.ibiblio.org/puppylinux/sf ... ce_216.sfs

[PenguinPupLin]

Thanks so much for pointing me in the right direction. My brief experience with Puppy Linux has been a happy yet challenging one with the kind assistance and generous guidance of such maestros as you two as well as a few others.

Is that why (a question I've posted in another thread) I ran into problem with Lighthouse Puppy 5.0.3 when I tried to compile the Nvidia 96 driver unsuccessfully i.e unable to compile Nvidia driver module - just after the message about gcc version check incompatibility (4.4 vs 4.3) where I was given a choice to go ahead and ignore it?

Edit: Sorry to trouble you again. A dense noob question, I downloaded the two files to /mnt/home as I did for other puppies but they didn't show up in the bootmanager config of Pup 214X so that I can select them for bootup. Copying the two files to the same subdir as Pup214X didn't help either.

[PenguinPupLin]

Just found out that the bootmanager config bootup will not list anything that has .xxx.sfs which is not .214.sfs.

Also sfs_load-1.2 is not supported by 214X-TOP9 whereas for sfs_load-1.3 while it sets up as a menu item,however failed to load the devx and source files after informing that " unionsf support is experimental ".

Hoped there is a workaround or solution for me. Thanks in advance.

Again,have asked this before but yet to get an answer,pardon my iteration,if only i can get swapfile to work in Classic Pup 214X-TOP9.

[Colonel Panic]

More problems I'm afraid.

I've had a few problems with the browsers in Top 9 (Aurora's given me some "fuzzing out" in some pages, and neither of the Seamonkeys I installed from Sully Sat's page would load at all unfortunately), but I've found success by installing the latest standard Seamonkey (2.6.1) in the /usr/lib directory. Even Flash works in it without any further installation or "fiddling about."

If my experience is at all typical, may I suggest Seamonkey for Top 10 when it's released?

CP .

[ttuuxxx]

Just found out that the bootmanager config bootup will not list anything that has .xxx.sfs which is not .214.sfs.

Also sfs_load-1.2 is not supported by 214X-TOP9 whereas for sfs_load-1.3 while it sets up as a menu item,however failed to load the devx and source files after informing that " unionsf support is experimental ".

Hoped there is a workaround or solution for me. Thanks in advance.

Again,have asked this before but yet to get an answer,pardon my iteration,if only i can get swapfile to work in Classic Pup 214X-TOP9.

swap files should be ext3, or ext2 and yes they work fine if they are made with 2.14x Gparted,
sfs need to be made with 2.14X, you can extract most sfs with the /root/SfS-converter/ I also made a update a few pages ago that will allow some wary sfs to work, you need to name them like. namegoeshere_214.sfs

[ttuuxxx]

More problems I'm afraid.

I've had a few problems with the browsers in Top 9 (Aurora's given me some "fuzzing out" in some pages, and neither of the Seamonkeys I installed from Sully Sat's page would load at all unfortunately), but I've found success by installing the latest standard Seamonkey (2.6.1) in the /usr/lib directory. Even Flash works in it without any further installation or "fiddling about."

If my experience is at all typical, may I suggest Seamonkey for Top 10 when it's released?

CP .

I've been working on Top 10 this weekend, It will take some time, I'm updating GTK2, and recompiling Gcc so that we can compile c++ apps properly,
ttuuxxx

[PenguinPupLin]

[snipped]

swap files should be ext3, or ext2 and yes they work fine if they are made with 2.14x Gparted,
sfs need to be made with 2.14X, you can extract most sfs with the /root/SfS-converter/ I also made a update a few pages ago that will allow some wary sfs to work, you need to name them like. namegoeshere_214.sfs

1) Does it mean swapfile created in ntfs partition will not work? As I've stated in my previous post here, my setup is a multi-boot environment of puppies with WinXP, all in ntfs partition, after first using puppy windows installer to set up Wary511 as the first frugal install - I didn't have any Linux ext2/3 partition as I was reluctant to shrink an existing WinXP boot partition and risk messing it up.

2) I'm not sure if I've understood you correctly,pardon my noob status,am I supposed to convert the devx_216.sfs and source file.216.sfs using the sfs-converter and rename them like namegoeshere_214.sfs in order for them to be listed in the bootconfig manager? If so, I hoped I can manage that, will give it a try.

It will be great if I can solve the swapfile problem and compile the Nvidia96 driver, the only two drawbacks for me as your Classic Pup 214X-TOP9 is certainly one of my favourites for my aged 10-yr-old notebook and other similar hardware.