I wouldn't consider mine low memory, something over 200mb. P2.

The cli-installer did start and ask if I wanted to partition. I don't; I'll look for a disk I'm willing to wipe tomorrow.

mckemie wrote:I wouldn't consider mine low memory, something over 200mb. P2.

The cli-installer did start and ask if I wanted to partition. I don't; I'll look for a disk I'm willing to wipe tomorrow.

cli-installer hangs after"y" to"repartition?". Wasn't able to locate cli-installer; expected to find it in /sbin, /bin, /usr/sbin, or /usr/bin.

Before I sent this, I noticed that cfdisk had finally loaded. Install went semi-smoothly. I ended up with a bootable drive. No browser. XTerm does not start. Few items on the right click menu. Some odd messages during the install and boot make me suspect a bad drive. I noticed that 20 gig drives can be bought for $14; if I don't find other drives around here, I will wait for a new one to arrive.

Boot parameter dpi=110 and dpi=150 seemed to have no effect. Backgrounds on the right click menuing system are cute but interfere with what needs to be read.

mckemie wrote:cli-installer hangs after"y" to"repartition?". Wasn't able to locate cli-installer; expected to find it in /sbin, /bin, /usr/sbin, or /usr/bin.

That's a reasonable expectation but almost all the antiX specific programs are in /usr/local/bin.

Before I sent this, I noticed that cfdisk had finally loaded. Install went semi-smoothly. I ended up with a bootable drive.

Great news!

No browser. XTerm does not start. Few items on the right click menu.

Some of this is because you are using a test iso. I was able to get the browser to start and also get a gui terminal. We use RoxTerm. This problem is my biggest concern ATM. I'm hoping they are just slow.

Some odd messages during the install and boot make me suspect a bad drive. I noticed that 20 gig drives can be bought for $14; if I don't find other drives around here, I will wait for a new one to arrive.

Linux is more chatty than it used to be. You can probably find many/most of these messages in the output of the dmesg program. You can use something like"dmesg | tail -n 100" to just see the last 100 lines.

Boot parameter dpi=110 and dpi=150 seemed to have no effect.

The way this works is that those boot parameters (and many others) work on the LiveCD. When you install from the LiveCD to your hard drive, all those settings get carried over but the boot parameters no longer work. I realize this is counter-intuitive. The reason for this strange setup is because"we" (the antiX team) have a lot of control over what happens when a LiveCD boots. But when you install, we have to make the system as Debian-like as possible which means we lose a lot of the control we once had. If we try to hang onto control by modifying startup files then our modifications can get lost in an upgrade causing mysterious failures.

If you are still using the default"slim" display manager then you can adjust the dpi by editing (as root) /etc/slim.conf and adding"-dpi 120" to the"xserver_arguments" line. One way to edit slim.conf is to open a terminal and run the"sux" command. Give it the root password when asked then run"leafpad /etc/slim.conf &". The"sux" program gives you root privileges and lets you open up windows as well on the desktop of a normal user.

The other way is to go to"Control Centre" -->"System""Edit Config files" and then pick the slim.conf tab.

Backgrounds on the right click menuing system are cute but interfere with what needs to be read.

You can toggle this with"Fluxbox settings" -->"Configuration""Transparency" -->"Force pseudo-transparency".

Normally, there are a variety of backgrounds to choose from.


I am delighted and relieved that you were able to install. It sounds like you are raring to go. I can think of three options, none of them perfect:

1. Sit and wait for the next release
2. Customize your current install and then make a custom cd for your other systems
3. Get a antiX-M11 cd modified to boot on your system and start from there.

I don't mind helping you get an antiX-M11 cd you can boot. My concern is that there are now 100's of Megs of updates that will need to be done (almost all of it is automatic). Logging and rebooting from X-windows will become broken until you fix the /etc/sudoers file. When the new release comes out I would suggest that you start over using that.

If you want to start installing programs now, you can run"sux" in a terminal window and then run:The thing is that once the new release comes out I would highly recommend that you switch over and start using that.

My biggest concern ATM is that you don't have a browser or a X-windows terminal (assuming RoxTerm is not working). You might find some clues in the log files in /var/log. I would try: