1. Hm. Odds are your old flux is in /usr/bin and the one you just installed is in /usr/local/bin. You'd probably be better off uninstalling flux first, then adding 0.9x, but I think I've got about three of them laying around various places. I can't remember how to check the version from within fluxbox. Try 'fluxbox -v' from a prompt and that'll tell you which one loads - or just compare what's where and what your path is. Anther thing about it is that you may want to 'mv .fluxbox .fluxbox.old' and let 0.9x generate a new configuration directory. There are some differences in the two versions. However, if you've put a lot of customizing into flux you might just try to doctor your current configs rather than replace them.

2. To make a terminal emulator transparent, all you need is one that's capable of it and a root window image the term can read. At one point, for complicated reasons, a combination of flux 0.1x and aterm couldn't do something I wanted, so I used Eterm and had to use Esetroot because Eterm is a picky little... anyway - you can get Eterm to work with others but it's simpler to give it what it wants. But with 0.9x or Ice, I could do what I wanted (transparent and borderless) so I quit using Eterm and Esetroot. Aterm doesn't care what you use to set the image. Check the man page for your term (and wm and X and so on ) to find out about stuff like this. You can issue it as an option every time you load aterm or just set 'aterm*transparent:true' (and more) in ~/.Xresources or ~/.Xdefaults.

I do not have an .Xresource or .Xdefaults?
Does this mean I do not have the Xrender?
Is there a config file that will auto config the aterm?
What I mean is can I set a predefined command for the aterms when they open... similar to

aterm -tr -tint blue -bg black -fg white

is this do able, so when I start X, I do not have to start all of my terminals with the commands?

i've attempted to reconfig the menu and the init file to see if it would work, but no luck.

Hm. Not sure if there's a workable file around to copy and edit - play around with editres and you'll get it. You can create the file or have editres dump a piece of one to get started. And read aterm's man page - it details the options. And editres'. And check out /etc/X11/app-defaults/

You could try something like

aterm*transparent:true
aterm*foreground: white
aterm*background: black
aterm*tinting: blue

Mine's

# aterm
aterm*transparent:true
aterm*shading: 50
aterm*foreground: green
aterm*background: black
aterm*scrollBar: False
aterm*saveLines: 1000
aterm*font: -misc-fixed-medium-r-normal-*-18-120-100-100-c-90-iso8859-2
aterm*reverseVideo: False

Or you could just alias it

alias aterm="aterm -tr -tint blue -bg black -fg white"

You'll need to restart X for .Xresources or restart a login shell in a term for those to take effect.

I do not have an aterm file in /etc/X11/app-defaults/.

I tried to insert
into the Editres file and rebooted fluxbox.
No luck
I think I may be misunderstanding.

can you expand on this...Do you mean for me to create an aterm file similar to the editres, or should I modify the editres to auto config my aterminal at activation?

would the xterm app-default control the aterm?

Sorry - I guess I wasn't being clear. I meant you could check out the files in /etc/X11/app-defaults/ to get an idea about how the specs worked. You won't have aterm in there. And editres is a tool you can use to change values, though it's kinda awkward. But playing around with it got it to sort of click for me. Um. Maybe I'd better quit trying to explain, as it seems to be doing more harm than good.

It's maybe not essential but you should try to restore the editres file you changed. Then, just... Hm. First, execute 'ls -al ~/.X[rd]*' in an xterm - want to make sure you don't have those. If you just get a prompt back, cool. So then open your favorite editor and paste in

aterm*transparent:true
aterm*foreground: white
aterm*background: black
aterm*tinting: blue

and then save it as .Xdefaults. (Mine's actually called .Xresources but it seems .Xdefaults is maybe preferred.) Then restart your X server. [-- edit: my mistake: it should actually take effect when you next launch aterm - no need to restart. But if it doesn't work, try restarting.] See, most every app will pay attention to that file and customize itself in ways it's not always easy to do with command line options. That's really the file you want to have and to edit.

As far as editres, type 'xcalc & editres &' - go to the 'commands' menu and click 'get tree' and click on xcalc. Click on 'bevel' - click 'show resource box' and you'll see a bunch of stuff. Click 'background' and type 'red' or whatever. Set your save file to '.Xresources.test' or something. Then click save and apply - maybe have to save it again separately. Editres can be weird. Anyway - your xcalc's border will turn red and you'll have a little file showing you what it looks like.

.xcalc.ti.bevel.background: red

You can make .Xdefaults out of that. Like the xcalc portion of my .Xdefaults is

#xcalc
.xcalc.ti.Command.background: lightgray
.xcalc.ti.bevel.screen*background: black
.xcalc.ti.bevel.screen*foreground: green
.xcalc.ti.bevel.background: darkgray

Looks a hell of a lot better. I dunno. Just play around with it. Or not. Just pasting that bit above into a filename should get your aterm going.

Or again, like I said back when - you could just alias it.

(1)
The ~/.Xdefaults file does not work. I created a ~/.Xresources file and it worked. How do you get the scroll bar transparent?
The following works, but the scroll bar is not transparent.
Is there a website that shows all of the commands you can put into the ./Xresources file?
aterm*transparent:true
aterm*foreground: white
aterm*background: black
aterm*tinting: blue
(2)
How do you scroll in the editries tool?
The tree is huge and runs off the screen, with no scroll bar to view the bottom entries.
(3)
I found another post you worked on.
http://www.linuxquestions.org/questi...t=.FXresources
I attempted to use the commands in my .Xresources file
aterm.dTitleBar: 0
aterm.dBorder: 0
They do not work.
I also attempted it like
aterm*dTitleBar: 0
aterm*dBorder: 0
What would it be for aterm?

1) aterm*scrollBar: False
2) I have no idea. I just move it up to the top and then drag the window border down to the bottom. Then you can (depending on your wm and configuration) move it around with 'alt+mouse drag' even if the title bar's off the screen. I don't use it much beyond the initial 'Ah ha!' time of figuring out the basic concept, so I never bothered to figure out that small detail. And some applications don't pay attention to it directly. They have to respond to its request and some choose not to. But most (all?) apps at least obey the Xresources file.
3) Sorry for any confusion again. That snippet isn't for Xresources but for a 'winoptions' file in IceWM. It doesn't work without Ice though there may be other ways to get the same effects depending on the application and the window manager. I'm just not sure how to do that other than with Ice.

X is really a disaster. I mean, it's an incredibly good and incredibly configurable thing and at the same time the default X apps have hardly changed since 1984 and it's an utter chaos of inconsistency. I like variety and dread the day we're all supposed to boot into KNOME by default but there's still a lack of consistent *methodology* and *syntax* within the variety.