(old)Puppy Linux Discussion Forum

Thanks partsman! Was just trying again before I saw your post - will try that out again shortly. So I jumped a step too far - typical Still getting some strange "error with mounting sr0" when trying to use Woofy and the iso on the cd burner - I suspect my ancient RW cd's are throwing small spanners in the remastering works. Burning afresh with new cds and will keep you posted
Cheers

I too get an error when I first try to mount SR0 but it always mounts on the second try
I am not sure why this happens Been that way since I started using Akita but never caused any problems Then again i have never used Woofy to remaster either

Puppyt wrote:Still getting some strange "error with mounting sr0" when trying to use Woofy and the iso on the cd burner

is that during woofy or using the jwm drive icons? I get it using the jwm desktop drive icons for CD drives... which my fault , not yours (or your CDs...) .. using the rox desktop fixes this for me..

Yes sc0ttman that is a better way of explaining it ! when you use JWM icon
But like I said always works 2nd time So far not a big deal

Thanks guys - I think I have to go back to Remastering-101 again though (after I get over this accursed man-cold). Yes, I was in the jwm drive-icon scenario. Just now I did a big remaster (628mb) with all the dosbox/dbgl/jre stuff installed first as pets. Nothing to show for it in the menus on bootup, unfortunately. I tried both in sc0ttman's 'novo' and partsman's 'respun' versions. Both in Woofy this time - looks like an absolutely indispensable tool. The right-click option on custom-puppy.iso for burn2cd dropped out early and coastered that particular cd unfortunately. (I noted too that after rebooting both OS's with their respective sfs' loaded on shutdown, hdd frugal installs, the sfs' fail to stay resident and ask to be re-loaded. Is this something you have seen before?) Hmm after a lie-down I'll start over, noting all my steps taken to report back to you to see where I might have tripped up. Off to buy more blank CD's - seems I should re-read the Akita thread a little more closely too, for the more obvious gotcha's,
Bye for now

I am sorry by a contribution with it being now when 3 years pass soon.
The following contents are originally shown and should be contributed soon.


Is Akita from Akita, Japan?


Akita (秋田) is the Japanese area(prefecture) name.

The kind of the dog includes "Akita-Inu". (秋田犬)
"Inu" (犬, or read with "ken") is Japanese and is a "dog".

The Akita-Inu is originally a big dog.
The Google photo result in the Japanese name:
https://www.google.co.jp/search?q=%E7%A ... C&tbm=isch


There was the attention from a name at first in Japan:

http://sakurapup.browserloadofcoolness. ... php?t=2070
(Forum of Japanese edition)

But problems occur frequently from-based Puppy
and do not spread in Japan...

It is unusual for distribution with the Japanese name to be born.
It was good and found it!

Because it was a thing written in by mistake, I deleted it.

Hi scottman, sorry if this has already been addressed but I couldn't find any reference in this thread - I'm convinced that the version of Isomaster in Akita is faulty (I'm testing with Akita 14 beta). It seems to carry a bug that has been in all of the 4.20 series pups. In short, isomaster creates an iso which seems good, and burns ok, but when used to boot generates the following message: I suspect this may only occur with certain isos, but I have not isolated it further yet. I can generate the failure consistently with the particular iso I am remastering and it seems to be the same fault that is referenced in these posts:

http://www.murga-linux.com/puppy/viewtopic.php?t=41101
http://208.109.22.214/puppy/viewtopic.p ... f30d411117

As far as I can tell the fault is triggered by the byte length of certain files in the iso, but the real culprit is the version of isomaster not being able to cope with those different file lengths.

If I use pup 431 to do the isomaster step it works perfectly, but if I use Akita14b isomaster I consistently create an iso that burns perfectly to an unbootable coaster. I suspect that you have not seen this fault because you probably always use woofy, and that obviously uses a different method of assembling the iso which avoids the "byte boundary" issue. Various posts also suggest that using the cli to manually do a mkiso works perfectly, but that doesn't help anyone who tries to use isomaster.

In the hope that you (or anyone...) has time to verify what I am saying (and hopefully identify a suitable version of Isomaster to replace the current one) here is the exact procedure I am using to consistently repeat the failure:

1) Download TurbopupAlpha3a from here:
https://ia801009.us.archive.org/4/items ... lpha3a.iso
(Save a copy of it on an external drive for later testing with the isomaster in pup431)
Boot Akita and copy this iso into /root.

2) Mount the iso and copy the pup_420turbo.sfs from the iso into /root (then unmount the iso)

3) Unsquash the sfs as follows: (a directory called squashfs-root is created and populated with the files from the expanded sfs)

Delete the original pup_420turbo.sfs from /root (to make room for the new one)

Reform the sfs (without making any changes) as follows: (This creates a new sfs that in theory should be exactly the same as the original one because we made no changes. In fact it seems to be slightly different in size, but ignore that as it does not affect the final functionality [even though it is this difference that probably triggers the faulty isomaster to be revealed...]. Save a copy of this new sfs on an external drive so that we can use it for further testing later

Start isomaster, look for the alpha3a iso in /root and doubleclick it so that you can see the contents displayed in the lower pane.

Click the pup_420turbo.sfs in the lower pane, then click "remove" so that the original sfs is now gone from the bottom pane.

In the upper pane (ie: displaying /root) click on the newly created pup_420turbo.sfs then click "add" so that it gets added into the lower pane.

Choose "file, save as" and save the new iso project as something like TurbopupAlpha3a_unsquashed_resquashed_isomastered.iso

Burn the iso to CD and try to boot from it. See if you get the same error as I do.

If so, try doing the last step again, but using puppy431 (which must have a different version of isomaster) ie: Boot into puppy 431, then add the TurbopupAlpha3 iso into /root and also copy the newly created sfs (which you made an external backup of...) into /root, and run isomaster again using the same method. In my testing the 431 isomaster copes perfectly with the files that Akita isomaster could not handle, and the CD burns and boots perfectly.

Hope you are still with me after all that ...
It would be great if you were able to verify this bug and incorporate a fix in the next version of Akita. (I'm hoping it is as simple as borrowing the isomaster from pup431). I think this bug created all sorts of problems for people who tried to remaster their 420 series pups and probably turned more than a few people off that version. Fortunately it looks like woofy came to the rescue, but still, I want to improve my remastering the more manual way first so I can understand how it all fits together...

greengeek, why not just copy the files you need into a folder named whatever you want your ISO to be called, then right click and choose 'Create file->ISO' ..?

sc0ttman wrote:why not just copy the files you need into a folder named whatever you want your ISO to be called, then right click and choose 'Create file->ISO' ..?

That'd be cheating

You're right - there are other ways to so this, but Isomaster just happened to be the method I learnt first and I like the "manual / visual" methodology of it. Do you think it might be possible to just replace the Akita Isomaster with the 431 version? (I've never compiled anything so there may be reasons why it's not that simple so I was waiting for your more experienced opinion)

greengeek wrote:

sc0ttman wrote:why not just copy the files you need into a folder named whatever you want your ISO to be called, then right click and choose 'Create file->ISO' ..?

That'd be cheating

You're right - there are other ways to so this, but Isomaster just happened to be the method I learnt first and I like the "manual / visual" methodology of it. Do you think it might be possible to just replace the Akita Isomaster with the 431 version?

I can give it a try ... or you can... wont hurt to test it ...

Thanks. I shall report back in a day or so..

I wanted to test Akita Linux too and so far so good.
I need to upgrade the Firefox browser from 17 to 26 sometjhing
first.

first problem issue. Akita don't allow that you symlink to a dir
or txt from sda1 to the pinboard. First time I had that problem.

Was it on purpose from the Dev?

nooby wrote:I wanted to test Akita Linux too and so far so good.
I need to upgrade the Firefox browser from 17 to 26 sometjhing
first.

first problem issue. Akita don't allow that you symlink to a dir
or txt from sda1 to the pinboard. First time I had that problem.

Was it on purpose from the Dev?

Akita disables the ROX pinboard by default...

To enable the ROX desktop, click on the desktop, choose Akita Setup, then click the 'Desktop Icons' button, and enable them (click Yes or something)...

Also, you can just click the update button in firefox, it will update to version 24 ... You must use the ESR Firefox version in Wary and Akita...

Ah okay that explains why it is way down in the menu list
too many things to consider. My brain goes black

I was doing a monthly boot up via USB with Akita(beta 14 I believe) and I got connected on my first try at work(WPA2 with Dougal's network wizard). I tried for a week to do it with Akita beta 16 and Partsman's version as well but both wouldn't hook up to my works WPA2 connection no matter what I tried but once I went to the older beta14, it hooked just fine.

My wireless hookup controller is an Intel PRO/Wireless 3945ABG(Golan) rev. 02 FYI. Any ideas why the older Akita beta worked but the newer one's didn't?

LoboGrande wrote:I was doing a monthly boot up via USB with Akita(beta 14 I believe) and I got connected on my first try at work(WPA2 with Dougal's network wizard). I tried for a week to do it with Akita beta 16 and Partsman's version as well but both wouldn't hook up to my works WPA2 connection no matter what I tried but once I went to the older beta14, it hooked just fine.

My wireless hookup controller is an Intel PRO/Wireless 3945ABG(Golan) rev. 02 FYI. Any ideas why the older Akita beta worked but the newer one's didn't?

No idea why that would be... Could go back over the changelogs, see what i changed/updated related to networking between those versions.. i always post the full changelogs... but i dont *think* i changed anything..

Sorry about the late (and useless response!)..

Hi sc0ttman
Hope you have been well ! Busy with puppy arcade I see
I haven't tried it yet but I will
I have to say there is an issue with acquiring dhcp address
It can be a real pain in the rump
I did not have these issues in b14
I don't know
Keep in touch

Well Partsman Akita14 version with the 2.6.32.28 kernel hooked up just fine with the secure wifi at work first time. My Toshiba Tecra M5 didn't like Chrome 7 in this version at all. Seamonkey 2.0.x and Firefox 13 are both crashy. Firefox 17ESR works fine QTWeb works fairly well,too but slower to load Flash heavy stuff like YouTube.

LoboGrande wrote:Well Partsman Akita14 version with the 2.6.32.28 kernel hooked up just fine with the secure wifi at work first time.

@LoboGrande
Glad that at leased you was able to get a wifi connection
The browsers are another issue but not limited to Akita ! Reading through the forums everyone struggles or gives pref. of diff. browsers Personally I
prefer seamonkey !
But I think you would agree Akita 14 did not have the wireless issues we have seen in b15 and up ! Would you agree ?
I am not sure what is diff But maybe sc0ttman does
I love the new package manger in b16 but the wifi prob is forcing me back to b14 I hope to see a diff in B17 release