UBCD V5.2b2 available for download
Moderators: Icecube, StopSpazzing
-
- Posts: 1368
- Joined: Mon Feb 21, 2005 10:59 pm
- Contact:
UBCD V5.2b2 available for download
UBCD V5.2b2 is available for download:
http://ubcd.mirror.fusa.be/ubcd52b2.iso
http://linuxfreedom.com/ubcd/download.html
md5sum: cc338cbd996072a137c38e6ec0c9d513
sha1sum: 5f9bfd3ff186be7eb815649f67474aa4682c5116
Changelog:
- Removed "/boot/syslinux/" from all COM32 entries in syslinux menus.
- Updated Gujin to V2.8.7. Thanks to Don Manuel for the update.
The updated index page is available here:
http://www.ultimatebootcd.com/v52/index.html
This is likely to be the last beta release. If there are no major showstoppers, next release will be 5.2.0.
I will revisit all app websites and update as required.
ady is still working on a way to build fdubcd.img from scratch using mtools and other free tools.
In the mean time, I would like to get this release out to see how well the superfloppy method works in the real world.
http://ubcd.mirror.fusa.be/ubcd52b2.iso
http://linuxfreedom.com/ubcd/download.html
md5sum: cc338cbd996072a137c38e6ec0c9d513
sha1sum: 5f9bfd3ff186be7eb815649f67474aa4682c5116
Changelog:
- Removed "/boot/syslinux/" from all COM32 entries in syslinux menus.
- Updated Gujin to V2.8.7. Thanks to Don Manuel for the update.
The updated index page is available here:
http://www.ultimatebootcd.com/v52/index.html
This is likely to be the last beta release. If there are no major showstoppers, next release will be 5.2.0.
I will revisit all app websites and update as required.
ady is still working on a way to build fdubcd.img from scratch using mtools and other free tools.
In the mean time, I would like to get this release out to see how well the superfloppy method works in the real world.
Re: UBCD V5.2b2 available for download
In "/ubcd/menus/grub4dos/system.lst", the "Hardware Detection Tool V0.5.2" entry is incorrect. It needs correction in the "/ubcd/tools/linux/syslinux2grub4dos/syslinux2grub4dos.sed" script so the resulting boot entry be adequate for grub4dos (most probably the two "/boot/syslinux/" relative path changes/editions in the script will correct this, but I have not tested it).
***
The current mkfdubcd (for fdubcd-custom.iso) scripts should not be included in UBCD, IMO. Currently there is no scripted replacement to customize the new fdubcd superfloppy, but leaving the old script for fdubcd-custom.iso will bring confusion for users and won't work in UBCD 5.2, as all fdubcd boot entries now expect a superfloppy. If a user needs to customize the new superfloppy, it would be useful and helpful to start a topic here in the forum.
***
The current mkfdubcd (for fdubcd-custom.iso) scripts should not be included in UBCD, IMO. Currently there is no scripted replacement to customize the new fdubcd superfloppy, but leaving the old script for fdubcd-custom.iso will bring confusion for users and won't work in UBCD 5.2, as all fdubcd boot entries now expect a superfloppy. If a user needs to customize the new superfloppy, it would be useful and helpful to start a topic here in the forum.
Re: UBCD V5.2b2 available for download
Victor,
Do you have any objection against using "FDUBCD_148 " as label for fdubcd.img, instead of the current "FDUBCD148 "?
Do you have any objection against using "FDUBCD_148 " as label for fdubcd.img, instead of the current "FDUBCD148 "?
-
- Posts: 1368
- Joined: Mon Feb 21, 2005 10:59 pm
- Contact:
Re: UBCD V5.2b2 available for download
Fixed. Thanks!In "/ubcd/menus/grub4dos/system.lst", the "Hardware Detection Tool V0.5.2" entry is incorrect.
You are right. Removed.The current mkfdubcd (for fdubcd-custom.iso) scripts should not be included in UBCD, IMO.
Rationale?Do you have any objection against using "FDUBCD_148 " as label for fdubcd.img, instead of the current "FDUBCD148 "?
Re: UBCD V5.2b2 available for download
The label is always padded with spaces up to 11 characters, and can be displayed by several tools (including 7zip under certain conditions, among others) as a filename using "8.3" format.Victor Chew wrote:Rationale?Do you have any objection against using "FDUBCD_148 " as label for fdubcd.img, instead of the current "FDUBCD148 "?
So
Code: Select all
12345678901 --> 12345678.901
FDUBCD_148 --> FDUBCD_1.48
FDUBCD_1481-->
FDUBCD_1.481
and it would still allow for the not-near future double digit versions, like 12.345:
FDUBCD12345-->
FDUBCD12.345
So, in short, the rationale would be a "fixed" alignment with the "dot" when displaying the version as an "8.3" file.
Last edited by ady on Sat Jan 26, 2013 10:12 pm, edited 1 time in total.
Re: UBCD V5.2b2 available for download
New memtest86 version released http://www.memtest86.com/change.html. Among other news:
Victor, since we are talking about RAM testing tools, I would suggest avoiding the "easy" method of using memdisk to boot the full ISO image.
In addition to the latest version, versions 3.5b and 4.0b are included in the official full release.Images for CD, USB key and Floppy disks now use Syslinux for booting and include a variety of standard options and two previous versions of Memtest86. The new boot time options may be specified at the boot prompt.
Victor, since we are talking about RAM testing tools, I would suggest avoiding the "easy" method of using memdisk to boot the full ISO image.
Re: UBCD V5.2b2 available for download
Suggestions:
In
change from:
COM32 /boot/syslinux/menu.c32
APPEND /ubcd/menus/syslinux/main.cfg
to:
(or, in other words, delete the first of those two original lines and change from "APPEND" to "CONFIG").
***
In
change from:
COM32 menu.c32
APPEND /ubcd/menus/syslinux/main.cfg
to:
***
In
change from:
COM32 menu.c32
APPEND /ubcd/menus/syslinux/*.cfg
to:
where *.cfg could be:
***
In
change from:
COM32 menu.c32
APPEND /ubcd/custom/custom.cfg
to:
***
In
change from:
COM32 menu.c32
APPEND /ubcd/menus/syslinux/*.cfg
to:
where *.cfg could be:
***
In
change from:
COM32 menu.c32
APPEND /ubcd/menus/syslinux/hdd.cfg
to:
where /ubcd/menus/syslinux/hdd/*.cfg could be:
***
In
_after_ the lines (#56 and #57):
add also the following two lines:
Note: The aforementioned additional "sed" code MUST be tested, as I can't be 100% sure that it will work as expected under all systems, specially because there are special characters involved (space, slash, ...). For example, there might be a situation where additional "quotation marks" (single, double or backslash) are needed in that "sed" code.
Victor, since we are already there in the "sed" file, please also review the lines still referring to fdubcd as iso image, so to correct them to new (super)floppy codes.
TIA,
Ady.
In
/boot/syslinux/syslinux.cfg
change from:
COM32 /boot/syslinux/menu.c32
APPEND /ubcd/menus/syslinux/main.cfg
to:
CONFIG /ubcd/menus/syslinux/main.cfg
(or, in other words, delete the first of those two original lines and change from "APPEND" to "CONFIG").
***
In
/ubcd/menus/syslinux/*.cfg
change from:
COM32 menu.c32
APPEND /ubcd/menus/syslinux/main.cfg
to:
CONFIG /ubcd/menus/syslinux/main.cfg
***
In
/ubcd/menus/syslinux/main.cfg
change from:
COM32 menu.c32
APPEND /ubcd/menus/syslinux/*.cfg
to:
CONFIG /ubcd/menus/syslinux/*.cfg
where *.cfg could be:
Code: Select all
bios.cfg
cpu.cfg
hdd.cfg
memory.cfg
others.cfg
periph.cfg
system.cfg
In
/ubcd/menus/syslinux/main.cfg
change from:
COM32 menu.c32
APPEND /ubcd/custom/custom.cfg
to:
CONFIG /ubcd/custom/custom.cfg
***
In
/ubcd/menus/syslinux/hdd.cfg
change from:
COM32 menu.c32
APPEND /ubcd/menus/syslinux/*.cfg
to:
CONFIG /ubcd/menus/syslinux/*.cfg
where *.cfg could be:
Code: Select all
main.cfg <<-- (already mentioned above)
bootmgmt.cfg
recovery.cfg
devmgmt.cfg
diag.cfg
cloning.cfg
editing.cfg
wiping.cfg
install.cfg
partmgmt.cfg
In
/ubcd/menus/syslinux/hdd/*.cfg
change from:
COM32 menu.c32
APPEND /ubcd/menus/syslinux/hdd.cfg
to:
CONFIG /ubcd/menus/syslinux/hdd.cfg
where /ubcd/menus/syslinux/hdd/*.cfg could be:
Code: Select all
/ubcd/menus/syslinux/hdd/bootmgmt.cfg
/ubcd/menus/syslinux/hdd/recovery.cfg
/ubcd/menus/syslinux/hdd/devmgmt.cfg
/ubcd/menus/syslinux/hdd/diag.cfg
/ubcd/menus/syslinux/hdd/cloning.cfg
/ubcd/menus/syslinux/hdd/editing.cfg
/ubcd/menus/syslinux/hdd/wiping.cfg
/ubcd/menus/syslinux/hdd/install.cfg
/ubcd/menus/syslinux/hdd/partmgmt.cfg
In
/ubcd/tools/linux/syslinux2grub4dos/syslinux2grub4dos.sed
_after_ the lines (#56 and #57):
Code: Select all
s|^CONFIG\(.*\)syslinux.cfg|configfile\1grub4dos.lst|
s|^CONFIG\(.*\)isolinux.cfg|configfile\1grub4dos.lst|
Code: Select all
s|^CONFIG /ubcd/menus/syslinux/\(.*\)\.cfg|configfile /ubcd/menus/grub4dos/\1\.lst|
s|^CONFIG /ubcd/custom/\(.*\)\.cfg|configfile /ubcd/custom/\1\.lst|
Victor, since we are already there in the "sed" file, please also review the lines still referring to fdubcd as iso image, so to correct them to new (super)floppy codes.
TIA,
Ady.
-
- Posts: 1368
- Joined: Mon Feb 21, 2005 10:59 pm
- Contact:
Re: UBCD V5.2b2 available for download
I think this is far too complicated.So, in short, the rationale would be a "fixed" alignment with the "dot" when displaying the version as an "8.3" file.
![Rolling Eyes :roll:](./images/smilies/icon_rolleyes.gif)
-
- Posts: 1368
- Joined: Mon Feb 21, 2005 10:59 pm
- Contact:
Re: UBCD V5.2b2 available for download
@ady: Points noted about memtest and the syslinux menu files. Thanks!
-
- Posts: 1368
- Joined: Mon Feb 21, 2005 10:59 pm
- Contact:
Re: UBCD V5.2b2 available for download
A simple chainloading of memtest86's syslinux.cfg seems to work fine:ady wrote:The new official memtest86's cfg file doesn't even use menu.c32 so to reduce the use of RAM before the test itself (it uses the old msg method to display a "menu"). You could either use the same method, or even merge the cfg and the msg files and use something like "COM32 menu.c32 mt86.cfg", or the CONFIG directive.
For memtest86, please avoid using all the unnecessary files in the ISO or the full ISO image with memdisk.
BTW, you can of course rename (from the official memtest images) "memtest.p" and "memtest.pp" to the 4.0b and 3.5b names respectively, already used in UBCD. And also the new "memtest" file can be renamed to its respective new version, 4.1.0.
The current "latest" version included in UBCD is replaced by the new 4.1.0 version.
BEWARE: in the official memtest86 cfg file, replace "kernel" with "linux".
Code: Select all
CONFIG /ubcd/boot/memtest86/syslinux.cfg /ubcd/boot/memtest86
![Very Happy :D](./images/smilies/icon_biggrin.gif)
Re: UBCD V5.2b2 available for download
All it needs is to use an underscore between FDUBCD and the "148" number. It was about aesthetics, and certainly not important in this particular case. I'm OK either way. The advantage of leaving it as it is now is that for version "10.00"Victor Chew wrote:I think this is far too complicated.
![Shocked :shock:](./images/smilies/icon_eek.gif)
![Mr. Green :mrgreen:](./images/smilies/icon_mrgreen.gif)
![Wink :wink:](./images/smilies/icon_wink.gif)
Although NOT for immediate release, I would suggest, eventually, an additional beta at some point, so users can have the opportunity to test and report back about the scripts, specially "syslinux2grub4dos" under different systems (Win9x, Win2k, WinXP..., Linux) and using different types of paths (different fs, with spaces,...).Victor Chew wrote:Points noted about memtest and the syslinux menu files.
It depends on the names you use for the kernels. Also, inVictor Chew wrote:A simple chainloading of memtest86's syslinux.cfg seems to work fine.
...
As usual, I will try to leave as much of the syslinux.cfg file as it is unless it gives us problems.
/ubcd/menus/syslinux/memory.cfgyou can now just leave one boot entry for memtest86 (3.5b, 4.0b, 4.1.0), since the new additional cfg file can provide the version selection. The reason for different versions could be provided in the boot entry's TEXT HELP in memory.cfg.
Re: UBCD V5.2b2 available for download
Hopefully, this post could potentially become some kind of tutorial.
The current Syslinux boot entry in UBCD52b2 for PMagic is:
I am suggesting here several (but simple) changes, so to make the (current and future) update of pmagic in UBCD easier and consistent.
Note: I hope Victor will accept these suggestions. If that turns out to be the case, the following "one-time-only" steps would be already done in the next release and they could be skipped from the following procedure.
Before I get into it, I want to make an important point. The following procedure is expressed in a generic way, so to try to cover (some) potential developments or changes that are not currently present in PMagic. That means that the following steps could be expressed in a _seemingly_ simpler way, by referencing specific words or codes as they are _currently_ expressed in PMagic. Instead, I decided to generalize the following steps, so not to be restrictive to what PMagic presents in current versions and thus covering at least part of potential future versions / variations / changes / developments in PMagic.
0_ For the purpose of this procedure, the structure of UBCD will be located at "
1_ (One-time-only step) In
2_ If present, delete the following unnecessary (and/or duplicated, and/or older, and/or incompatible) files from UBCD:
3_ Copy (or directly move, if you are confident about what you are doing) and overwrite files from "
3.1_ The content of "
3.2_ Almost all the content of "
In some cases, it might be easier to first copy all the content of "
In some cases, it might be easier to _first_ delete the unnecessary files (the aforementioned exceptions) from "
4_ Open the new "
5_ In each of the new "
5.1_ Optionally, from to where "
Please note that the initial and ending space characters in both codes MUST be used in that last code replacement.
5.2_ From "
5.3_ From to Note the initial (but no ending) space character in both codes.
5.4_ This code replacement involves several c32 Syslinux modules, and there are several alternative ways to achieve it (by using "Regular Expressions", for example).
"
Note the initial (but no ending) space character in both codes.
Examples:
change from to and from to
Note that there might be other c32 Syslinux modules mentioned in pmagic's *.cfg file(s) (like "linux.c32" for example), that may be using different paths (or no path at all) than the one used in that code replacement, so they are not (and shall not be) included in this specific step, as expected.
5.5_ From to If necessary, this step could be coded in a more generic way, so to match some additional potential c32 Syslinux modules. For example, the ones mentioned in the previous step would be
5.6_ From "
6_ Now save the opened *.cfg files. The new "
The above steps of this procedure are "generic enough" to be used with future versions of PMagic. If someone can "translate" the above manual procedure into scripts (using the same techniques and auxiliary tools as the current UBCD scripts), it could be useful too.
The current Syslinux boot entry in UBCD52b2 for PMagic is:
Code: Select all
CONFIG /pmagic/boot/syslinux/syslinux.cfg /pmagic/boot/syslinux/
Note: I hope Victor will accept these suggestions. If that turns out to be the case, the following "one-time-only" steps would be already done in the next release and they could be skipped from the following procedure.
Before I get into it, I want to make an important point. The following procedure is expressed in a generic way, so to try to cover (some) potential developments or changes that are not currently present in PMagic. That means that the following steps could be expressed in a _seemingly_ simpler way, by referencing specific words or codes as they are _currently_ expressed in PMagic. Instead, I decided to generalize the following steps, so not to be restrictive to what PMagic presents in current versions and thus covering at least part of potential future versions / variations / changes / developments in PMagic.
0_ For the purpose of this procedure, the structure of UBCD will be located at "
ubcd_extracted". Download a new updated version of PMagic and extract it to some directory; let's call it "
pmagic_extracted".
1_ (One-time-only step) In
ubcd_extracted/ubcd/menus/syslinux/main.cfgchange the aforementioned boot entry from: "
CONFIG /pmagic/boot/syslinux/syslinux.cfg /pmagic/boot/syslinux/" to:
Code: Select all
CONFIG /pmagic/boot/syslinux/syslinux.cfg /pmagic/
Code: Select all
ubcd_extracted/pmagic/boot/syslinux/*.c32
ubcd_extracted/pmagic/boot/syslinux/*.bin
ubcd_extracted/pmagic/boot/syslinux/iso*.*
ubcd_extracted/pmagic/boot/syslinux/iso*
ubcd_extracted/pmagic/boot/syslinux/memdisk
ubcd_extracted/pmagic/pmodules/PMAGIC*.SQFS
pmagic_extracted" into "
ubcd_extracted/pmagic/" as follows:
3.1_ The content of "
pmagic_extracted/pmagic/" (including subdirectories) into "
ubcd_extracted/pmagic/".
3.2_ Almost all the content of "
pmagic_extracted/boot/" (including subdirectories) into "
ubcd_extracted/pmagic/boot/"; with the exception of the following files:
Code: Select all
pmagic_extracted/boot/syslinux/*.c32
pmagic_extracted/boot/syslinux/*.bin
pmagic_extracted/boot/syslinux/iso*.*
pmagic_extracted/boot/syslinux/iso*
pmagic_extracted/boot/syslinux/memdisk
pmagic_extracted/boot/" (including subdirectories) into "
ubcd_extracted/pmagic/boot/" at once, and then delete the unnecessary files (the above exceptions) from "
ubcd_extracted/pmagic/boot/syslinux/".
In some cases, it might be easier to _first_ delete the unnecessary files (the aforementioned exceptions) from "
pmagic_extracted/pmagic/boot/syslinux/", and then copy all the remaining content of "
pmagic_extracted/boot/" (including subdirectories) into "
ubcd_extracted/pmagic/boot/" at once. I personally find this 3rd alternative method to be easier.
4_ Open the new "
ubcd_extracted/pmagic/boot/*.cfg" file(s) in some simple text editor (Notepad could be used, but other text editors are better suited to deal with Unix-like newlines).
5_ In each of the new "
ubcd_extracted/pmagic/boot/*.cfg" file(s), we need to apply the "Replace all" function several times, as follows (in this precise order; and the specific order is indeed important):
5.1_ Optionally, from
Code: Select all
" initrd=/pmagic/initrd.img " (without the quotation marks)
Code: Select all
" iso_filename=/path/to/ubcdNN.iso initrd=/pmagic/initrd.img " (without the quotation marks)
iso_filename=/path/to/ubcdNN.iso" in the official UBCD 5.2 release would be "
iso_filename=ubcd52.iso"; and for user's customization the "
iso_filename=/path/to/ubcdNN.iso" path and file name shall be adapted to the user's needs.
Please note that the initial and ending space characters in both codes MUST be used in that last code replacement.
5.2_ From "
/boot/" (without the quotation marks) to "
boot/" (without the quotation marks). This step effectively deletes the first slash "/" character. Note that this "Replace all" might temporarily mess up some code that was already adequate for our needs. The unwanted result will be corrected in next steps. The reason to use such a generic replacement code is to support potential future changes in pmagic.
5.3_ From
Code: Select all
" boot/syslinux/memdisk" (without the quotation marks)
Code: Select all
" /boot/syslinux/memdisk" (without the quotation marks)
5.4_ This code replacement involves several c32 Syslinux modules, and there are several alternative ways to achieve it (by using "Regular Expressions", for example).
Replace allfrom "
boot/syslinux/*.c32" to
"
/boot/syslinux/*.c32" (adds the first slash "/" character).
Note the initial (but no ending) space character in both codes.
Examples:
change from
Code: Select all
" boot/syslinux/menu.c32" (without the quotation marks)
Code: Select all
" /boot/syslinux/menu.c32" (without the quotation marks)
Code: Select all
" boot/syslinux/reboot.c32" (without the quotation marks)
Code: Select all
" /boot/syslinux/reboot.c32" (without the quotation marks)
5.5_ From
Code: Select all
"COM32 linux.c32" (without the quotation marks)
Code: Select all
"COM32 /boot/syslinux/linux.c32" (without the quotation marks)
"COM32 menu.c32"and
"COM32 reboot.c32".
5.6_ From "
/pmagic/" (without the quotation marks) to "" (without the quotation marks). The new replacement (or second) code is empty, with no character at all, so the first code is deleted from the cfg file(s). Note that there shall NOT exist any space character in these codes, at all. Also note that the initial and ending slash "/" characters are required in the (first) code to be replaced (or, in this case, in the code to be deleted).
6_ Now save the opened *.cfg files. The new "
ubcd_extracted" structure can be used either on a USB drive or to build a new UBCD ISO image. The "
pmagic_extracted" directory is not required anymore.
The above steps of this procedure are "generic enough" to be used with future versions of PMagic. If someone can "translate" the above manual procedure into scripts (using the same techniques and auxiliary tools as the current UBCD scripts), it could be useful too.
-
- Posts: 34
- Joined: Mon Nov 19, 2012 11:18 pm
Re: UBCD V5.2b2 available for download
Parted Magic 2013_01_29 is out
https://sourceforge.net/projects/parted ... 013_01_29/
https://sourceforge.net/projects/parted ... 013_01_29/
-
- Posts: 1368
- Joined: Mon Feb 21, 2005 10:59 pm
- Contact:
Re: UBCD V5.2b2 available for download
There _will_ be a 5.2b3 due to the scope of the changes.Although NOT for immediate release, I would suggest, eventually, an additional beta at some point
Done.Also, in /ubcd/menus/syslinux/memory.cfg, you can now just leave one boot entry for memtest86 (3.5b, 4.0b, 4.1.0), since the new additional cfg file can provide the version selection.
Note. Thanks!Parted Magic 2013_01_29 is out: https://sourceforge.net/projects/parted ... 013_01_29/
-
- Posts: 178
- Joined: Fri Jun 17, 2011 11:23 pm
Re: UBCD V5.2b2 available for download
Sorry for cross-posting (if any), but I think F-prot can be updated as well.
See my post for info: viewtopic.php?p=24543#p24543
See my post for info: viewtopic.php?p=24543#p24543