Must be the early morning. I don't quite understand this bit. Could you pls elaborate?

Quote:

Some Syslinux files were NOT updated to the latest version.

Holy *@&#! Not again! Which ones?

Quote:

Any reason for not to keep support for booting PartedMagic 6.0 from the Grub4Dos menu?

Grub4dos has been dropped from PM quite a few versions back, and the discrepancies between the old and the new has been getting larger and larger. It will not be easy to update and sync between the two.

Quote:

but there is no such file "grub4dos.lst" under the "/pmagic/boot/syslinux/" folder.

Will have to update syslinux2grub4dos to filter out these entries when translating to grub4dos.

Must be the early morning. I don't quite understand this bit. Could you pls elaborate?

The version of diskchek included in UBCD51a3 is not the same as it was before. I checked, and redownloaded the latest version from their site. There is no update either. So something has happened with the files in diskcheck.img.gz. Is this happening only to me?

Quote:

Quote:

Some Syslinux files were NOT updated to the latest version.

Holy *@&#! Not again! Which ones?

This time I did not check each and everyone. I stopped at the first discrepancy I found:

Code:

<ubcd51a3-extracted>\boot\isolinux\isolinux.bin

Quote:

Quote:

but there is no such file "grub4dos.lst" under the "/pmagic/boot/syslinux/" folder.

Will have to update syslinux2grub4dos to filter out these entries when translating to grub4dos.

There are several entries of those in several different configuration files in UBCD51a3, according to the specific files where PMagic tools were included (to start PMagic from that line).

The version of diskchek included in UBCD51a3 is not the same as it was before. I checked, and redownloaded the latest version from their site. There is no update either. So something has happened with the files in diskcheck.img.gz. Is this happening only to me?

Same file as in 5.1a2. MD5sum is fea200a3c23941ae3d6c4e6a681ada77.

Quote:

This time I did not check each and everyone. I stopped at the first discrepancy I found:Code:<ubcd51a3-extracted>\boot\isolinux\isolinux.bin

As I explained in our private PM, this is the only file that is different, and I can't explain it. So I have written a new diff script to check all syslinux files against the original to make sure they are the same before release in the future.

There are some tool executables/files that have the same checksum codes than in previous versions, but the file names and "modified dates" are different.

This changes also leads to unnecessary changes in the CABs / ZIPs /GZips...

Testing and comparing between ubcd releases is more difficult doing these unnecessary changes, and the xdelta is bigger.

If the only reason for these changes is because of lower case / upper case changes, IMO it is not worth it.

Moreover, the tools should have the same "modification date" (and the same letter/case) as the original tools downloaded from their original websites.

Making these little changes makes more difficult to find tools that need updates, or to find which version is already included.

"Nicer" capital letters should not be such a problem, since listing the files in a DOS cmd or under a real DOS is not the primary use of these files.

Moreover, changing a file "name" should NOT change its "modification date", but for some reason, this kind of changes *are* happening.

Both kind of changes ("modified date" and upper case) are going to change also the resulting CABs. This is undesirable. The only reason for changing a CAB archive should be a real, necessary and desirable change in its contents.

A similar example of this type of unnecessary changes is the modification date of syslinux-related files. Those files have a "modified date" different from the original, which makes finding old version that were not correctly updated even more difficult.

The actual process or procedure that makes the tools inside CABs to be modified might not be the same as the ones changing the syslinux-related files, but the undesirable consequences are almost the same.

Please use the original files to build the archives (CABs, ZIPs, 7Zips, GZips, IMGs, ISOs...), so it will be easier to compare, follow and test new releases of UBCD.

Both final versions (DOS16 and DOS32) include the same updated sys.com and the same updated country.sys, among other useful general batch files.

The difference between both packages is in the kernel.sys. Both packages also include relevant documentation.

The latest version listed in FreeDOS.org is 2038, but the listed versions there are not always the latest available, which in this case is 2039.

These files are updated versions when comparing against those in FreeDOS 1.0, but even those included in FreeDOS 1.0 are more up-to-date than the ones included in FDUBCD.

I hope at least part of these files can be updated/included into the next FDUBCD, which should make it not only more up-to-date, but also more compatible with FreeDOS 1.0 (as the comparison of the arguments available in sys.com show).

To make it clear, the kernel.sys DOS32 version 2039 file of this package are already updated in UBCD, but some others (like sys.com), are not.

2011-04-21 2:02 On April 16, Jack Ellis again updated his excellent UIDE and other drivers (RDISK, XMGR). This is a minor update re-adding caching capability for other DOS drivers. Grab binaries and sources at http://johnson.tmfc.net/dos/driver.html . EDIT: (Apr. 25) "BAD initialization error is corrected in UIDE, UIDEJR, and RDISK (XMGR not affected)!"

From the homepage:

Quote:

XMGR, RDISK, and UIDE are DOS drivers for an 80386+ system using MS-DOS V5.0+, FreeDOS, and all similar DOS variants.

Quote:

XMGR is a DOS XMS memory manager. It supports V3.70+ UMBPCI by Uwe Sieber and can load directly into UMBPCI upper-memory. XMGR also runs with JEMM386/JEMMEX, MS-DOS V4.49/V4.95 EMM386 or other similar "EMS managers". It is written to V3.0 XMS Specifications and supports up to 4-GB of memory.

Quote:

RDISK is a DOS RAM-disk driver, which creates a "fast" disk drive using 2 Megabytes to 2 GIGABYTES of XMS memory

Quote:

UIDE is a "Universal IDE" caching driver for DOS.

Quote:

UIDE also supports up to 8 CD/DVD drives, which may be SATA, UltraDMA, or old "PIO mode" models.

Quote:

The small UIDEJR driver ["junior" UIDE] is available.

@Victor, I think that it may be interesting to explore these drivers for FDUBCD.

Who is online

Users browsing this forum: No registered users and 5 guests

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 post attachments in this forum