Thanks secipolla.

I have decided to replace pcmanfm with thunar. Thunar appears to be fast and light and does a much better job of mounting/unmounting external devices. Halevt is broken now that there is no /etc/init.d/hal and any upgrade of halevt fails to install correctly. Best to remove it.

Of course, pcmanfm is in the repo for those that want it.

For antiX-base, halevt is replaced by usbmount. It is not perfect, but it is not broken and devices should show in Rox under /media/usb. Do make sure you unmount the device in Rox (right click, unmount) before removing the stick as you might find your mouse or keyboard not working. If you install thunar in base, then it is best to remove usbmount.

I have decided to replace pcmanfm with thunar

Good. I have been reading up on Thunar Tips and Tricks lately. I was thinking of axing pcmanfm for thunar anyways on my 8.5 installs.

I don't know if it's larger or not but if you're gonna have Thunar then you could replace gnomebaker for xfburn as well maybe.

Thinking about that as well secipolla.

i'm for thunar and for xfburn as well, if they don't bring to many dependencies. gnome baker is crashing at a usual pace on my machine and on two other computers. i use recorder when i burn something, once on every full moon.

How about xfe as a file manager for X11?
- xfe, xfe-themes, libfox-1.6-0, and xfe-i18n together maybe 4000kb package size/10000kb installed size.
- thunar, thunar-data and a few other specific dependencies take up more space.
What's better, dunno. Trying both right now, 'tho.

drg, xfe is a fine file manager, but we need a file manager that can auto-mount usb devices. xfe cannot do so. Thunar seems to be the best light(ish) way to do so now halevt is broken.

My ten cents worth says go for Thunar. I may end up using an alternative, but for sure the newest version of pcmanfm is a major disappointment.

Thunar does not have tabs but in Fluxbox that is no problem.
Thunar's custom actions are enough reason for me to install it on whatever distro I am using, with any window manager or desktop environment.
Xfburn is, according to many who have used both, more reliable.

A ROX and Thunar combo would be awesome!!

I've also used xfburn and found it worked quite well.

Hah, back again after some hopping about and a bit of real life with ailing rellie. Oddly enough the first couple of times I tried to boot this rc1 full live cd on this machine, ThinkPad Z60m, it just stopped dead right at the start of boot. Could have been cosmic rays? Reboot after a couple of hours with Archbang, right as rain. No probs on a Dell D610 laptop last night.

Booted with ath5k wifi PC Card still in Z60m, needed it for Archbang which doesn't have ipw2200 fw. Wicd a bit confused. Hmmm, it wants the builtin wifi to be eth0, ie the Intel 2915=ipw2200. Usually this is eth1. I had to tell wicd what interface to use.

eth0 IEEE 802.11g ESSID:"foo"
Mode:Managed Frequency:2.462 GHz Access Point: xxx
Bit Rate:48 Mb/s Tx-Power=20 dBm Sensitivity=8/0
Retry limit:7 RTS thr:off Fragment thr:off
Encryption key:morefoo Security mode:open
Power Management:off
Link Quality=93/100 Signal level=-35 dBm Noise level=-91 dBm
Rx invalid nwid:0 Rx invalid crypt:0 Rx invalid frag:0
Tx excessive retries:0 Invalid misc:0 Missed beacon:1

eth1 no wireless extensions.

wlan0 IEEE 802.11bg ESSID:off/any
Mode:Managed Access Point: Not-Associated Tx-Power=0 dBm
Retry long limit:7 RTS thr:off Fragment thr:off
Encryption key:off
Power Management:off

Maybe some refinement needed for wicd config at boot detecting what wifi interfaces are present? Some distros seem to have the magic on this. Come to think of it, perhaps Partition Magic has the power on that front?

I see hardinfo says there is no battery in this laptop. That's not correct, I hope :-/ Maybe some missing module in hardinfo, something to do with acpi?

Not seeing any problem with periodic disconnect to internet via wifi at present, unlike previous post.

From rc1 full CD on a Compaq Armada E500 600MHz P3 laptop w/320MB RAM. Via wifi using a PC Card with Ralink rt2561s. Problem at first boot when I tried to use the RutilT wlan manager. This brought on a storm of dialogue boxes multiplying to fill the screen. 'An error occured Code:22 Can't get frequency/channel'. This was BAD. Eventually had to power cycle the machine, as couldn't get a terminal to respond. Maybe the runaway was saturating the CPU. Anyway, this should never happen. Something to look into?

Wicd is working OK but I had to set prefs such that wlan0 was not the wired interface as wicd first thought. In fact the machine has no builtin lan port. Connected now via wifi and WPA with TKIP/PSK, think that's the right jargon.

The delay at boot for selecting options is not long enough imho as mentioned previously. 15 secs minimum and maybe some kind of 'booting in 10-9-8 secs' indicator. Maybe there is one I've missed because it boots so fast?

I booted into fluxbox - when I tried to change wallpaper away from the default monochrome blobby thing and selected apply to fluxbox, the new wallpaper only appears on part of the screen -such as the area where conky displays, window title bar and the panel at the bottom of the screen. What does it mean?

Hope this helps in some small way.

root@antiX1:~# ps_mem.py
Private + Shared = RAM used Program

60.0 KiB + 8.5 KiB = 68.5 KiB acpi_fakekeyd
128.0 KiB + 17.5 KiB = 145.5 KiB gpm
128.0 KiB + 29.5 KiB = 157.5 KiB gnome-pty-helper
140.0 KiB + 43.0 KiB = 183.0 KiB ck-launch-session
156.0 KiB + 28.5 KiB = 184.5 KiB init
164.0 KiB + 52.5 KiB = 216.5 KiB hald-addon-leds
184.0 KiB + 35.0 KiB = 219.0 KiB cron
172.0 KiB + 52.5 KiB = 224.5 KiB hald-addon-acpi
172.0 KiB + 52.5 KiB = 224.5 KiB hald-addon-rfkill-killswitch
176.0 KiB + 53.5 KiB = 229.5 KiB hald-addon-input
208.0 KiB + 50.0 KiB = 258.0 KiB hald-runner
248.0 KiB + 36.5 KiB = 284.5 KiB acpid
420.0 KiB + 12.0 KiB = 432.0 KiB dhclient
324.0 KiB + 135.0 KiB = 459.0 KiB hald-addon-storage (2)
388.0 KiB + 117.0 KiB = 505.0 KiB su
376.0 KiB + 135.5 KiB = 511.5 KiB gvfsd
440.0 KiB + 132.0 KiB = 572.0 KiB getty (6)
420.0 KiB + 162.0 KiB = 582.0 KiB gvfs-afc-volume-monitor
484.0 KiB + 147.5 KiB = 631.5 KiB gvfs-gphoto2-volume-monitor
612.0 KiB + 41.5 KiB = 653.5 KiB wpa_supplicant
636.0 KiB + 74.5 KiB = 710.5 KiB halevt
640.0 KiB + 307.0 KiB = 947.0 KiB polkitd
668.0 KiB + 292.0 KiB = 960.0 KiB gconfd-2
776.0 KiB + 232.5 KiB = 1.0 MiB gvfs-gdu-volume-monitor
964.0 KiB + 45.0 KiB = 1.0 MiB rsyslogd
372.0 KiB + 789.5 KiB = 1.1 MiB udevd (3)
824.0 KiB + 344.0 KiB = 1.1 MiB dbus-daemon (2)
644.0 KiB + 537.5 KiB = 1.2 MiB udisks-daemon (2)
988.0 KiB + 358.0 KiB = 1.3 MiB console-kit-daemon
1.1 MiB + 275.5 KiB = 1.4 MiB cupsd
1.1 MiB + 340.5 KiB = 1.4 MiB conky
1.0 MiB + 453.5 KiB = 1.5 MiB slim
2.6 MiB + 105.0 KiB = 2.7 MiB hald
2.6 MiB + 636.5 KiB = 3.2 MiB fluxbox
3.5 MiB + 709.5 KiB = 4.2 MiB wicd-monitor
2.9 MiB + 1.6 MiB = 4.5 MiB roxterm
3.4 MiB + 1.6 MiB = 5.1 MiB rox
5.4 MiB + 551.5 KiB = 5.9 MiB wicd
10.4 MiB + 857.5 KiB = 11.2 MiB bash (3)
10.2 MiB + 2.7 MiB = 12.9 MiB wicd-client
27.9 MiB + 1.1 MiB = 29.0 MiB Xorg
51.2 MiB + 2.7 MiB = 53.9 MiB iceape-bin
---------------------------------
152.7 MiB
=================================

Private + Shared = RAM used Program

Still up on E500 after 8h 40mins. Around 7h 30 Iceape crashed when I inadvertently followed a link to a heavily burdened MSM newspaper site. However it started up again with several tabs open. This is a live session btw with no swap on the disk which has only Win XP on it.

I have been seeing periodic disconnects while using wicd. Unclear on what is causing these. Can't see a reason in wicd log, maybe I don't know what to look for. Thought it may have been related to periods of inactivity and screen blanking but it just happened while I was actively using the browser.

Thanks for the feedback all.

gnomic, make sure you use the correct option when changing fluxbox wallpaper. If you have icons, then use Apply to Rox-fluxbox.

rutilt is there as an extra. IMHO it is much better to use ceni or wicd. wicd is not configured, but it the standard default used in Debian.
iceape crashing on MSN is a feature __{{emoticon}}__

When I run an apt-get upgrade on M11 using smxi I get an error message about not being able to update initramfs and that I can over ride this by running initramfs-update with the"t" option.
Is this necessary, needed, harmful?
Everything seems to work OK without running the update.