@Scoticus,tlchost,
This may simply display my ignorance for the world to see, but I feel compelled to ask. When I have burned multisession CDs using burniso2cd I have never been able to verify them. This leaves open the possibility you did not have a good burn, which would explain your problems, even if the ISO had a good md5 sum.
Q: does anyone have a simple way to verify a multisession CD against the ISO file that produced it? Could this be incorporated in burniso2cd ?
Minisys-Linux Muppy 008.3 F (July, 12th, 2008)
-
prehistoric
- Posts: 1744
- Joined: Tue 23 Oct 2007, 17:34
good burn?
Last edited by prehistoric on Tue 13 May 2008, 11:05, edited 1 time in total.
Minisys-Linux Muppy 008.3b (may,08,2008)
Mark
Multisession DVD+RW is my standard method of working with Puppy. I have had no problems with burning ISOs on these disks and working with them.
I hope this is of assistance
Multisession DVD+RW is my standard method of working with Puppy. I have had no problems with burning ISOs on these disks and working with them.
I hope this is of assistance
I updated the Mini-Isos and the addons.sfs.
Changes:
- Goggles fix (black window)
- Cups now is in the Mini, not in the addons.
There is one issue with it though:
addons_083.sfs must NOT be loaded, when you want to set up a printer in the Cups Webinterface.
If it is loaded, the Cups Webserver has permission-problems.
I see no logic issue for this, and cannot fix that.
So to setup a printer, remove addons_083.sfs from the bootmanager, and reboot first.
The updated addons have Cups removed and the fixed Weather-Gdesklet.
Mark
Changes:
- Goggles fix (black window)
- Cups now is in the Mini, not in the addons.
There is one issue with it though:
addons_083.sfs must NOT be loaded, when you want to set up a printer in the Cups Webinterface.
If it is loaded, the Cups Webserver has permission-problems.
I see no logic issue for this, and cannot fix that.
So to setup a printer, remove addons_083.sfs from the bootmanager, and reboot first.
The updated addons have Cups removed and the fixed Weather-Gdesklet.
Mark
Last edited by MU on Thu 15 May 2008, 06:41, edited 1 time in total.
[url=http://murga-linux.com/puppy/viewtopic.php?p=173456#173456]my recommended links[/url]
I updated the Standard-Isos with the latest fixes (Weather-Gdesklet, Goggles). They also now include all the games from the latest update of games.sfs.
So everything is synchron and requires no external patches any more until new issues are reported.
The build-system (c) currently uploads, it will take 1-2 hours.
Mark
So everything is synchron and requires no external patches any more until new issues are reported.
The build-system (c) currently uploads, it will take 1-2 hours.
Mark
[url=http://murga-linux.com/puppy/viewtopic.php?p=173456#173456]my recommended links[/url]
Re: good burn?
I just had to replace my DVD/RW drive....which was the reason I could not remaster a LIVECD. Even though the drive was bad, burniso2cd told me the image was burned correctly. Now, with a new drive that does burn correctly, burniso2cd tells me that the burn was bad. I watched the drive during the process, and it appears that the new drive is slightly slower to initially spin up...perhaps that is what burniso2cd sees.prehistoric wrote:@Scoticus,tlchost,
When I have burned multisession CDs using burniso2cd I have never been able to verify them.
Thom
Sound trouble
Speaking of Muppy Mini 008. Running Impress the powerpoint files shows the slides show correctly but with no sound.
Then, I installed ppview.exe using the w$(wine) entry with same result.
With Gxine, Mplayer, sound is OK
Some idea?
Xan
Then, I installed ppview.exe using the w$(wine) entry with same result.
With Gxine, Mplayer, sound is OK
Some idea?
Xan
-
prehistoric
- Posts: 1744
- Joined: Tue 23 Oct 2007, 17:34
X race condition
@MU,
I've been provoked into going public on a change to 3.02 before I had tested it enough. fix for X race I'm posting from a Muppy 008.3 installation where I've applied this and it seems to work for this case as well. You can find the whole long story of the hunt for this snark in this thread.
I've been provoked into going public on a change to 3.02 before I had tested it enough. fix for X race I'm posting from a Muppy 008.3 installation where I've applied this and it seems to work for this case as well. You can find the whole long story of the hunt for this snark in this thread.
I uploaded version 008.3d.
Changes:
- includes gstreamer + exaile (Mediamanager/player) from the former "goodies.sfs".
- includes optional propriatary ATI graficsdrivers for Radeon-cards 7000 - 9250, that must be installed outside X by typing "install-ati" (to remove: "uninstall-ati")
- fixed symlink for smb.conf, so that samba-shares now should work in Minisys
- fixed wrong permissions in /usr using the addons.sfs for the Mini. That prevented Cups to work, now it works.
The buildsystem was updated, too.
Mark
Changes:
- includes gstreamer + exaile (Mediamanager/player) from the former "goodies.sfs".
- includes optional propriatary ATI graficsdrivers for Radeon-cards 7000 - 9250, that must be installed outside X by typing "install-ati" (to remove: "uninstall-ati")
- fixed symlink for smb.conf, so that samba-shares now should work in Minisys
- fixed wrong permissions in /usr using the addons.sfs for the Mini. That prevented Cups to work, now it works.
The buildsystem was updated, too.
Mark
[url=http://murga-linux.com/puppy/viewtopic.php?p=173456#173456]my recommended links[/url]
Muppy 008.3
sorry - accidental double post
Last edited by Barburo on Thu 22 May 2008, 06:27, edited 1 time in total.
Muppy 008.3
Hi Mark,
I'm enjoying your latest Muppy - using Opera browser for the first time seriously and liking it.
When I click on the task bar paw mark and make a selection from the menu - it works. Close that application or window.
Click again on the paw mark and the last selection automatically is restarted!
Close again and task bar menu allows me to select another item. However upon closing that item and reclicking the same thing happens again.
Is it a bug? (I scrolled through this thread but couldn't find any reference to this but I may have missed something).
I also notice via conky the greater use of the swap partition vs RAM on my notebook than for other Puppies based on 3.01 - is there a reason for this?
Thanks for your efforts on this and your tireless attention in responding to us Puppy Muppy-ites.
I'm enjoying your latest Muppy - using Opera browser for the first time seriously and liking it.
When I click on the task bar paw mark and make a selection from the menu - it works. Close that application or window.
Click again on the paw mark and the last selection automatically is restarted!
Close again and task bar menu allows me to select another item. However upon closing that item and reclicking the same thing happens again.
Is it a bug? (I scrolled through this thread but couldn't find any reference to this but I may have missed something).
I also notice via conky the greater use of the swap partition vs RAM on my notebook than for other Puppies based on 3.01 - is there a reason for this?
Thanks for your efforts on this and your tireless attention in responding to us Puppy Muppy-ites.
[i]Laptop[/i]: Acer Aspire 5810TZ
Menu:
I can't reproduce the menu issue on my system, but remember I had something like this on my notebook.
I will use my notebook the whole next week, and then try to find out, why it is so.
Might be a delay-issue in the code.
Swap:
yes, Puppy is loaded to Ram if you have enough of it. If the swap is very big, the Kernel puts seldom used stuff from Ram to swap.
- I have a desktop with 1 Gb Ram, and a big swap.
Then the system is loaded to Ram, and if I use Standard, 600 MB of swap is used, so almost the whole msy_083.sfs is in swap!
For this reason I use the mini on this system, here swap is 0%, later just 20% running firefox, gimp and more (which are in addons.sfs mounted directly from disk, it is not buffered in Ram).
- On my notebook (256 MB Ram), the standard works better.
It is mounted of the disk, because it does not fit in Ram, that anyway is pretty fast.
So it is not swapped, and Ram stays free completely for applications.
If I use the Mini here, it is loaded to Ram, leaving not much free Ram for applications, so also gets swapped. That seems to be a bit slower.
On the website I wrote, that the Mini is always better.
This seems not to be true in every case, depending on your Ram and swap-settings.
Best will be to try out both versions.
Mark
I can't reproduce the menu issue on my system, but remember I had something like this on my notebook.
I will use my notebook the whole next week, and then try to find out, why it is so.
Might be a delay-issue in the code.
Swap:
yes, Puppy is loaded to Ram if you have enough of it. If the swap is very big, the Kernel puts seldom used stuff from Ram to swap.
- I have a desktop with 1 Gb Ram, and a big swap.
Then the system is loaded to Ram, and if I use Standard, 600 MB of swap is used, so almost the whole msy_083.sfs is in swap!
For this reason I use the mini on this system, here swap is 0%, later just 20% running firefox, gimp and more (which are in addons.sfs mounted directly from disk, it is not buffered in Ram).
- On my notebook (256 MB Ram), the standard works better.
It is mounted of the disk, because it does not fit in Ram, that anyway is pretty fast.
So it is not swapped, and Ram stays free completely for applications.
If I use the Mini here, it is loaded to Ram, leaving not much free Ram for applications, so also gets swapped. That seems to be a bit slower.
On the website I wrote, that the Mini is always better.
This seems not to be true in every case, depending on your Ram and swap-settings.
Best will be to try out both versions.
Mark
[url=http://murga-linux.com/puppy/viewtopic.php?p=173456#173456]my recommended links[/url]
-
prehistoric
- Posts: 1744
- Joined: Tue 23 Oct 2007, 17:34
CUPS permissions in standard ISO?
@MU,
Mark, I think I went to the wrong site and picked up an older Muppy standard ISO. I used the links on the Minisys English language page to download. Because the file names don't reflect the letter changes from 008.3c to 008.3d I could easily have confused the two.
I'm reportiing this as a bug anyway, because you said the permission problem with CUPS applied to the mini version and the workaround was to install the printer without the addons.sfs file. The standard ISO has no addons.sfs. So, what to do in that case?
Regarding bandwidth consumed by all the people downloading ISOs, how about easily available pets, sfs or xdeltas for the change from 008.3 to 008.3d? (Make the full download a little harder.)
Mark, I think I went to the wrong site and picked up an older Muppy standard ISO. I used the links on the Minisys English language page to download. Because the file names don't reflect the letter changes from 008.3c to 008.3d I could easily have confused the two.
I'm reportiing this as a bug anyway, because you said the permission problem with CUPS applied to the mini version and the workaround was to install the printer without the addons.sfs file. The standard ISO has no addons.sfs. So, what to do in that case?
Regarding bandwidth consumed by all the people downloading ISOs, how about easily available pets, sfs or xdeltas for the change from 008.3 to 008.3d? (Make the full download a little harder.)
old versions get a version-number, so they still can be downloaded browsing the ftp-folders.
The current version always has the original name, so that the links on the website always will lead to the current version, without modifying them (what could cause cache-problems).
current (version 008.3d):
Muppy-Minisys-Linux-Standard-008.3-EN.iso
old:
Muppy-Minisys-Linux-Standard-008.3-EN.iso-old-c
Concerning deltas: I must have a look how this works, at moment I'm too busy.
The quickest way for me to create upgrades (still using many hours) is to run my buildscripts, then upload. Adding more choices, would cost more time.
Except if I just add small changes, then I release a new goodies.sfs or update-dotpup.
Addons: they are for the Mini-Iso only, to give it the same functionality as Standard.
Addons.sfs is not for theStandard-Iso!
The Cups permission problem was only related to Mini, not to Standard.
Mark
The current version always has the original name, so that the links on the website always will lead to the current version, without modifying them (what could cause cache-problems).
current (version 008.3d):
Muppy-Minisys-Linux-Standard-008.3-EN.iso
old:
Muppy-Minisys-Linux-Standard-008.3-EN.iso-old-c
Concerning deltas: I must have a look how this works, at moment I'm too busy.
The quickest way for me to create upgrades (still using many hours) is to run my buildscripts, then upload. Adding more choices, would cost more time.
Except if I just add small changes, then I release a new goodies.sfs or update-dotpup.
Addons: they are for the Mini-Iso only, to give it the same functionality as Standard.
Addons.sfs is not for theStandard-Iso!
The Cups permission problem was only related to Mini, not to Standard.
Mark
[url=http://murga-linux.com/puppy/viewtopic.php?p=173456#173456]my recommended links[/url]
-
prehistoric
- Posts: 1744
- Joined: Tue 23 Oct 2007, 17:34
CUPS problem solved
Mea culpa, Mark, 
The problem was not with CUPS. I picked up the wrong driver twice, for well-known printers: Samsung ML-1710, Canon BJC-210. (The Canon driver has been around since approximately the time programmers first descended from the trees. That's why it is one of my standard fall-back tests.) Getting exactly the right PPD file from linuxprinting.org made the difference. The way it failed resembled some permission problems I've had on other systems.
I can understand why the BJC-210 driver would not be included in a recent package, the Samsung ML-1710 is another matter; it is only two or three years old and was sold in large numbers.
To err is human, even when you're prehistoric.
The problem was not with CUPS. I picked up the wrong driver twice, for well-known printers: Samsung ML-1710, Canon BJC-210. (The Canon driver has been around since approximately the time programmers first descended from the trees. That's why it is one of my standard fall-back tests.) Getting exactly the right PPD file from linuxprinting.org made the difference. The way it failed resembled some permission problems I've had on other systems.
I can understand why the BJC-210 driver would not be included in a recent package, the Samsung ML-1710 is another matter; it is only two or three years old and was sold in large numbers.
To err is human, even when you're prehistoric.
next week (up to 10 days) we go to companies to install things.
So in that time, I cannot work on 008.4.
I plan for 008.4, to upgrade Gtk to slackware-gnomes version.
Then I also would replace the Gnome related files with those of Gnome 2.22.
As the Standard iso is 690 MB already (with localization), I then must check the size, and what I will drop from it (games?) to get space for more printerdrivers. Or it would no longer fit on a CD, that of course would be inacceptable.
Then I could try to add more printer-drivers from one of the pets, that were posted here (I think there was a pack called "cups-heaven" or so with many recent drivers).
Mark
So in that time, I cannot work on 008.4.
I plan for 008.4, to upgrade Gtk to slackware-gnomes version.
Then I also would replace the Gnome related files with those of Gnome 2.22.
As the Standard iso is 690 MB already (with localization), I then must check the size, and what I will drop from it (games?) to get space for more printerdrivers. Or it would no longer fit on a CD, that of course would be inacceptable.
Then I could try to add more printer-drivers from one of the pets, that were posted here (I think there was a pack called "cups-heaven" or so with many recent drivers).
Mark
[url=http://murga-linux.com/puppy/viewtopic.php?p=173456#173456]my recommended links[/url]
Here are pets for TESTING to make Muppy 008.3 french and dutch:
ftp://ks301128.kimsufi.com/Muppy0083/FRANCAIS/ (updated version from may, 28, 2008)
ftp://ks301128.kimsufi.com/Muppy0083/NETHERLANDS/
I wanted to try it myself, but I am actually too busy with development - no time.
Please backup your msy_save.2fs , then install the pet.
Please report us your experiences.
Here is the private message I received with this pet:
I received it on may, 6th, so sorry for the delay
As I said, I wanted to test it myself first, but there were those bugs I had to fix first...
As the next 2 weeks I'm busy, too, I now delegate the testing to all interested users.
---------------------------------------------------------------------------
Bonsoir Mark,
Tout d'abord un grand merci pour cette nouvelle version de Muppy, j'aime beaucoup.
Je suis occupé à terminer le paquet de localisation Muppy008.3-FR.pet et actuellement je le teste sur la version Mini DE. En gros cela fonctionne plutôt bien mais j'ai observé certaines curiosités :
- Je suis systématiquement obligé de télécharger (commande Chooselocale) fr_FR même s'il se trouve déjà dans mon paquet. Si je ne le fais pas, je n'obtiens pas la traduction de toutes les applications en FR.
- Je n'arrive pas à obtenir la traduction en français des entrées de menus. Par contre, si je modifie un seul fichier .desktop situé dans /usr/share/applications/ alors, après enregistrement de la modification, brusquement tout le menu principal se traduit en français.
- Je n'obtiens pas la traduction des textes des icônes sur le bureau, elles restent en allemand. Pourtant j'ai bien un fichier Translate-ROX.mo traduit en français. Bon, là c'est moins grave, on peut les traduire en français depuis le bureau.
Voila où j'en suis. J'ai aussi réactualisé mon site et ouvert un espace pour la Muppy afin d' y placer un manuel d'utilisation en Français.
J'ai aussi produit un paquet Muppy-NL et l'ai envoyé à Béèm le 3 Avril pour voir s'il pourrait s'occuper des fichiers .desktop en NL, mais il ne m'a pas donné de nouvelles depuis. S'il n'est pas intéressé, je demanderai à mon frère de me trouver quelqu'un en Belgique.
Les paquets se trouvent ici :
http://www.softenpoche.com/sep/Muppy-FR08.3.pet
http://www.softenpoche.com/sep/Muppy-NL.pet
Bonne soirée et à bientôt
--
gw
ftp://ks301128.kimsufi.com/Muppy0083/FRANCAIS/ (updated version from may, 28, 2008)
ftp://ks301128.kimsufi.com/Muppy0083/NETHERLANDS/
I wanted to try it myself, but I am actually too busy with development - no time.
Please backup your msy_save.2fs , then install the pet.
Please report us your experiences.
Here is the private message I received with this pet:
I received it on may, 6th, so sorry for the delay
As I said, I wanted to test it myself first, but there were those bugs I had to fix first...
As the next 2 weeks I'm busy, too, I now delegate the testing to all interested users.
---------------------------------------------------------------------------
Bonsoir Mark,
Tout d'abord un grand merci pour cette nouvelle version de Muppy, j'aime beaucoup.
Je suis occupé à terminer le paquet de localisation Muppy008.3-FR.pet et actuellement je le teste sur la version Mini DE. En gros cela fonctionne plutôt bien mais j'ai observé certaines curiosités :
- Je suis systématiquement obligé de télécharger (commande Chooselocale) fr_FR même s'il se trouve déjà dans mon paquet. Si je ne le fais pas, je n'obtiens pas la traduction de toutes les applications en FR.
- Je n'arrive pas à obtenir la traduction en français des entrées de menus. Par contre, si je modifie un seul fichier .desktop situé dans /usr/share/applications/ alors, après enregistrement de la modification, brusquement tout le menu principal se traduit en français.
- Je n'obtiens pas la traduction des textes des icônes sur le bureau, elles restent en allemand. Pourtant j'ai bien un fichier Translate-ROX.mo traduit en français. Bon, là c'est moins grave, on peut les traduire en français depuis le bureau.
Voila où j'en suis. J'ai aussi réactualisé mon site et ouvert un espace pour la Muppy afin d' y placer un manuel d'utilisation en Français.
J'ai aussi produit un paquet Muppy-NL et l'ai envoyé à Béèm le 3 Avril pour voir s'il pourrait s'occuper des fichiers .desktop en NL, mais il ne m'a pas donné de nouvelles depuis. S'il n'est pas intéressé, je demanderai à mon frère de me trouver quelqu'un en Belgique.
Les paquets se trouvent ici :
http://www.softenpoche.com/sep/Muppy-FR08.3.pet
http://www.softenpoche.com/sep/Muppy-NL.pet
Bonne soirée et à bientôt
--
gw
Last edited by MU on Fri 30 May 2008, 10:08, edited 1 time in total.
[url=http://murga-linux.com/puppy/viewtopic.php?p=173456#173456]my recommended links[/url]
-
prehistoric
- Posts: 1744
- Joined: Tue 23 Oct 2007, 17:34
test results
@MU,
I just ran a series of tests which could provoke an interesting response on a support line. I used a 1 GHz !GB RAM machine with a DVD drive to install Muppy 008.3d to a refurbished Seagate 500 GB IDE drive. (This was a frugal install to /dev/hda1.) The machine used a GeForce3 video adapter to drive a 21" SGI flatscreen CRT at 1600x1200x24 @ 85 Hz.
I then moved the drive to a machine which has revealed problems in several other distributions - a 500 MHz 128 MB RAM Compaq iPaq (desktop) with neither CD/DVD nor floppy, using the Intel eepro100 network interface.. This machine uses embedded i810 graphics with shared video memory to drive a 17" IBM G78 flat screen CRT at 1024x768x24 @ 85 Hz.
I'm posting from the second machine. After rerunning xorgwizard, I had no serious problems. You don't recommend running the Muppy standard installation on a machine with such limited memory, (and I understand why,) but it works.
Some minor problems:
The message window which asks about installing intel graphics drivers is too small for the title to be read. On a 1600x1200 screen this looks pretty silly. There needs to be a notice in the green body of the window which can be read without enlarging the window. Also, Hotpup calculates screen positions without considering the height of the taskbar. On the 1600x1200 screen this meant the device icon labels were unreadable.
The disk I used has a 2 GB swap partition, (for testing purposes.) Several times on that iPaq I had a hang at "unmounting swap". Suspecting a problem with processes left over from exiting X, I applied the hack I've used on "Chihuahua" alpha 6 to deal with a race condition in X. This seems to have solved the problem, though half a dozen shutdowns and reboots is not a real test.
On slow machines the probability of getting the message about "no pinboard in use" on power up approaches 1. I'm thinking there is a race condition between pinboard startup and wm startup. This could also apply to the problem with icon pileups and the nvidia driver. Adjusting timing isn't a general solution. Could you point me toward documentation about using ROX under other window managers, like Icewm? I'm dealing with similar issues on "Chihuahua".
I just ran a series of tests which could provoke an interesting response on a support line. I used a 1 GHz !GB RAM machine with a DVD drive to install Muppy 008.3d to a refurbished Seagate 500 GB IDE drive. (This was a frugal install to /dev/hda1.) The machine used a GeForce3 video adapter to drive a 21" SGI flatscreen CRT at 1600x1200x24 @ 85 Hz.
I then moved the drive to a machine which has revealed problems in several other distributions - a 500 MHz 128 MB RAM Compaq iPaq (desktop) with neither CD/DVD nor floppy, using the Intel eepro100 network interface.. This machine uses embedded i810 graphics with shared video memory to drive a 17" IBM G78 flat screen CRT at 1024x768x24 @ 85 Hz.
I'm posting from the second machine. After rerunning xorgwizard, I had no serious problems. You don't recommend running the Muppy standard installation on a machine with such limited memory, (and I understand why,) but it works.
Some minor problems:
The message window which asks about installing intel graphics drivers is too small for the title to be read. On a 1600x1200 screen this looks pretty silly. There needs to be a notice in the green body of the window which can be read without enlarging the window. Also, Hotpup calculates screen positions without considering the height of the taskbar. On the 1600x1200 screen this meant the device icon labels were unreadable.
The disk I used has a 2 GB swap partition, (for testing purposes.) Several times on that iPaq I had a hang at "unmounting swap". Suspecting a problem with processes left over from exiting X, I applied the hack I've used on "Chihuahua" alpha 6 to deal with a race condition in X. This seems to have solved the problem, though half a dozen shutdowns and reboots is not a real test.
On slow machines the probability of getting the message about "no pinboard in use" on power up approaches 1. I'm thinking there is a race condition between pinboard startup and wm startup. This could also apply to the problem with icon pileups and the nvidia driver. Adjusting timing isn't a general solution. Could you point me toward documentation about using ROX under other window managers, like Icewm? I'm dealing with similar issues on "Chihuahua".
the pinboard is run from /root/.xinitrc
you could try a delay:
Mark
Code: Select all
rox -p /root/Choices/ROX-Filer/PuppyPinCode: Select all
sleep 3 && rox -p /root/Choices/ROX-Filer/PuppyPin &[url=http://murga-linux.com/puppy/viewtopic.php?p=173456#173456]my recommended links[/url]
@MU: I was excited when you mentioned about Muppy server on another post regarding sharing files on the network.
I wanted to try it on an old Compaq Ipaq Celeron with an external USB wireless (at76_usb - i guess is the name of the module). This module worked fine on other Puppy systems for the same USB wireless. But on this old machine, the module loads, but there is no connection.
If this worked, I could make some use of this old pc.
If you have time, please do help.
I wanted to try it on an old Compaq Ipaq Celeron with an external USB wireless (at76_usb - i guess is the name of the module). This module worked fine on other Puppy systems for the same USB wireless. But on this old machine, the module loads, but there is no connection.
If this worked, I could make some use of this old pc.
If you have time, please do help.
[url=http://macpup.org][b]Macpup - The beauty of linux[/b][/url] [b] | [/b] [url=http://pritlog.com/][b]Pritlog - Simple blog app[/b][/url]
Hi Mark - some more feedback:
I downloaded mini and all the .sfs files.
addons.sfs may have an incorrect MD5 sum - I downloaded it twice (once via browser, once via wget) and I got identical files - the same MD5 but different from yours.
I have an old PC I tried Standard and Mini on it - a Celeron 634, 320 Mb RAM, and my swap file on disk is 867Mb.
When I loaded Standard I was able via xorg to get a good screen resolution (1280x1024).
I loaded mini as a fresh install and xorg was only successful at very low resolutions (680x840 or something like that).
I ran mini again but picked up the previous .2fs save file from Standard and everything worked - good resolution etc.
Any idea why?
I downloaded mini and all the .sfs files.
addons.sfs may have an incorrect MD5 sum - I downloaded it twice (once via browser, once via wget) and I got identical files - the same MD5 but different from yours.
I have an old PC I tried Standard and Mini on it - a Celeron 634, 320 Mb RAM, and my swap file on disk is 867Mb.
When I loaded Standard I was able via xorg to get a good screen resolution (1280x1024).
I loaded mini as a fresh install and xorg was only successful at very low resolutions (680x840 or something like that).
I ran mini again but picked up the previous .2fs save file from Standard and everything worked - good resolution etc.
Any idea why?