(old)Puppy Linux Discussion Forum

I can vouch for mac OS-X snow-leopard, and boot's too.

01micko wrote:I can vouch for mac OS-X snow-leopard, and boot's too.

So HFS is not required for Mac?


Sigmund

Rockridge format for DVD is the best for Mac users
but Joliet works as well. Older formats like HFS still work on a Mac DVD drive
probably ?? but I haven't tested on recent Macs.

_____________________________________________

I just booted a macbook air with slacko-5.5 burnt with Pburn from an external CD drive. AFAIK, HFS is the old mac filesystem, currently HFSPLUS is the filesystem on the system disk. (I mounted it ro in slacko, but that is too off topic, Makato, see PM soon).

Previously, we had a vanilla macbook (circa 2009, w/Superdrive) that handled disks burnt with Pburn just fine.

HTH

Here is next try

I think it would be best to avoid slang expressions, for the sake of people with less English Maybe you could say something like this (although I guess translators would then need to find out what term is actually used for "Level 1" in their languages):
Old "Level 1" standard (8.3 naming)

Regarding Macs, from the information I've seen, only pre-OSX Macs should require HFS, and then they may require the -part option as well. But I don't have one to test, and I'm wondering if they even require more work.

disciple wrote:I think it would be best to avoid slang expressions, for the sake of people with less English Maybe you could say something like this (although I guess translators would then need to find out what term is actually used for "Level 1" in their languages):
Old "Level 1" standard (8.3 naming)

You're right!
Could it be just "Old standard (8.3 naming)"?

Sure, but personally I prefer "very old" or "really old"

Here's how the wikki describes it

The standard has three different levels for files, here paraphrased from section 10:
Level 1: File names are limited to eight characters with a three-character extension, using upper case letters, numbers and underscore only. The maximum depth of directories is eight.
Level 2: File names are not limited to 11 characters (the 8.3 format) but can be up to the maximum allowed by the 1 byte counter in the directory entry and the filename length byte counter. Typically, this is close to 180 characters, depending on how many extended attributes are present.
Level 3: Files are allowed to be non-contiguous (i.e., fragmented), principally to allow packet writing or incremental CD recording.

So I would suggest "Old format -8.3 file naming (not recommended)"
or

"8.3 file naming (not recommended)"


You should discourage people from using that format,
since it radically changes the file names so that
it becomes difficult to recognize the file again.

______________________________________

Another 2c
DOS 8.3 naming (deprecated)

Feature Request
It doesn't appear to be possible to filter file windows to specific filetypes such as .iso files. See attached screen grab from attempting to import an ISO on Pburn 3.7.18 - the actual ISOs were quite a way down the list.

With regard to the discussion on changing burn option windows, I note that zigbert's example grab shows a nice Info button and an Advanced tab. The latter would be a handy place for explicitly stating the burn options where the simplified options won't suffice for the target system.

01micko wrote:Another 2c
DOS 8.3 naming (deprecated)

That's too OS-specific, some older versions of RISC OS will also only read CDs with 8.3 naming. IIRC native Joliet support only came in with RISC OS 4.x. The relevant filing system is CDFS so "DOS" is meaningless in that context.

Just having it as "8.3 naming (deprecated)" will do - it's succinct and one can make a reasonable assumption that only people that know they need it are likely to select it anyway.

Jades wrote:The latter would be a handy place for explicitly stating the burn options where the simplified options won't suffice for the target system.

Yes, but I don't think they need checkboxes and things for them. If there's an unusual combination of options someone knows they want to use, then allowing them to manually edit the command should be sufficient.

Jades wrote:Feature Request
It doesn't appear to be possible to filter file windows to specific filetypes such as .iso files. See attached screen grab from attempting to import an ISO on Pburn 3.7.18 - the actual ISOs were quite a way down the list.

It is possible to filter the content of the file-window, BUT that requires opening the file-window from an entry+button. Not from a menuitem as when import iso-image. (If this sounds like non-sense and bullshit, I totally agree with you. But it is still the way how gtkdialog works ). It could maybe be fixed by a invisible entry+button that are called from the menuitem, but at the same time, I want to keep the code uncluttered.


Sigmund

Does thunor know about that issue?

Hi guys,

I burned a few DVDs with Pburn while on Puppy Linux and now they show up empty on Windows Vista.

I was using a Toshiba A200 with Windows Vista that crashed and I had to run the recovery cd. Before doing so, I put a usb pen on my Asus EEE 901 with Lubuntu, installed Unetbootin and created a Puppy Linux Live usb pen. I booted this on my Toshiba (which was freezing upon boot, so this was the only possibility), and used Pburn to backup files before runing the recovery cd.

The recovery cd was run, the system was recovered and the Toshiba is now running Vista again as new. However, the dvds I burned before in Puppy Linux with Pburn show as empty.

What can I do?

Thank you in advance,
Francisco

You're a bit off-topic, but can you read them in Puppy?

Yes, I can.
I can boot Puppy through the pen and simply copy paste the content of each dvd after mounting the "windows" hard-drive.

Is there a better topic to post about Pburn?

No, but it seemed like you were asking about how to read those CDs, more than about the apparent problem with Pburn.

Lekium
You want pBurn 4

Unfortunately it is not released yet


Sigmund