Apt 1.3b1

Summary:

Beta: get them while they're hot

page 1 of 212next »

Apt 1.3b1

Pent 18 Aug 2008 08:30

Dear Users,

Apt 1.3b1 (full version only) is available earlier than expected. You can find it at:

http://apt.dinglisch.net/SECRETDIRECTORY/apt1.3b1.zip

(replace SECRETDIRECTORY with the directory you received in your
registration email)

Please note that this is a BETA version, meaning it contains new features
that have not been extensively tested and that your device should
be backed up before installing it.

I'm going to be AFK for a few days so you have time to find all the bugs :-)

---

To upgrade from 1.2:

- disable 'Enabled' and 'Enable After Reset' in Apt settings
- exit Apt
- backup your existing AptDB.pdb to minimally 10 locations on at least 5 continents.
- reset device
- install 1.3b1 (don't forget the new AptAssist.prc)

---

To upgrade from 1.0/1.1:

- install and run 1.2 (to upgrade your DB)
- proceed as above

---

1.3b1 will upgrade your AptDB to a new version: you CANNOT use Apt 1.2 with the DB once it has been upgraded.

If you are getting problems with Apt disabling itself for no apparent reason,
please try installing…

http://lee.dinglisch.net/palm/squeak/squeak1.3b.zip

…and when Apt disables run Squeak and Menu->Show Apt Status

Please keep complaints about disabling to the thread about disabling.

Pent

changes.txt

1.3b1 18/08/2008
- IMPORTANT: only compatible with an Apt 1.2 DB. If you are upgrading from a prior version, you
should install Apt version 1.2 first to upgrade your DB.
- changed Brgth:DSet (set *Defaults* brightness) to Brgt:Copy (copy current system value to *Default* brightness)
Note: be careful, you need to set brightness first if using some form of brightness dimming
- FExit trigger now checks argument against both form name and ID
- put a divider before Remove in Menu->Apt
- increased max macro/menu length to 100
- added …/Beep, argument is "freq(Hz),duration(ms)", vol comes from game sound level
- default Apt priority is now V High, some treo/centro users report that helps with some
problems
- added Hard/Power to simulate power button being pressed. The intended use is to allow
wakeup of the device with e.g. a Time trigger, before performing some other action
- added repeater argument for triggers oHrd1-4 (-> opt+hardbutton press-and-hold)
- bugfix: don't handle char triggers when in menu (was messing up menu item selection)
- bugavoidance: removed WhiteOnBlack theme from thirdparty/KhromaDB.pdb, problems reported by different
users on different devices
- bugfix: star menu doesn't crash after selection in Blazer and friends
- bugfix press-n-hold popups don't crash after selection in Blazer and friends
- bugfix: get tap/get stroke don't crash after doing the stroke etc in Blazer and friends
- force DB sync after write when resident (was getting empty DB after reset sometimes) (does this help ?)
- bugfix: removed small fonts on T3, required system call not available
- bug avoidance: refuse to launch DAs in Blazer and friends
- bug avoidance: don't allow held-button unlock triggers in Blazer and friends
- bugfix: don't turn off everything when only going to rem sleep (thanks for hint Chastreo!)
- tersified some error messages, make space
- moved splash screen to app launch (not so annoying coming from settings)
- screen lock during loading
- start with all UI items invisible (cleaner/faster startup)
- bugfix: was not exiting cleanly when problems at startup
- removed excess flag when powering off, maybe help with disable condition ?
- bugfix: UI: when two identical triggers were in adjacent rows, changing the arg or condition
of the first would propogate down to the second (thanks Don/Stefan)
- bugfix: UI: bad window handle error on sim fixed (though it didn't seem to affect
anything on device)
- improved removal process, Centro (maybe more) had problems
- UI: 'Loading' message changed slightly

Re: Apt 1.3b1

SportyRydr 19 Aug 2008 02:09

- bugfix: star menu doesn't crash after selection in Blazer and friends

I was so excited about this, but, alas…

A reset was caused on 8/18/08 at 2:07 pm while running "Web": Window68K.c, Line:86, No shadow window found

which I've seen from some other apps in the previous version, but hadn't had time to post yet. (It just sounds like the contents of the underlying menu hasn't been saved?) This not only happened when I tried to launch MetaDA from a Star menu in Blazer, but also when I chose the Rcnt list from that Star menu (same error). In fact, before a Star menu didn't necessarily crash Blazer (for me), but launching a DA. I remember, because I used to have to time the trigger (hrd4 hold 1) so I would know the menu was there (since it wasn't displayed) and could press the button I wanted (e.g., NavR=Rcnt). Now, the menu displays, but trying to use it crashes with the "no shadow window" error.

- bug avoidance: refuse to launch DAs in Blazer and friends

If 'bug avoidance' means it no longer resets, then the avoidance isn't working on my 755. That is, if I correctly understand the fix: when I choose MetaDA from my Star menu, using the NavL button, it should ignore that and either leave the menu displayed or dismiss the menu and do nothing? (Does that 'bug avoidance' designation mean you're giving up trying to fix it? ;u)

Using the center button to select a Star menu item passes the press through to the underlying app. For example, if I set the center button to "… Back", then the application that Back sends me to gets a center button press when it launches, and if that button does anything in that particular app, then that thing will happen as soon as the app launches. For example, in PowerMan, the center button pops up a menu for the currently selected profile.

Sorry I didn't post these things sooner (except for the first one), but who knew you'd be so snappy getting 1.3b out? :u) I tend to save things up that I find when I'm bug testing.

No disabling, so far, and the menu hotkeys work again…great! :uD

Last edited on 19 Aug 2008 02:15 by SportyRydr Show more

Re: Apt 1.3b1

donl517 18 Aug 2008 14:10

"p.s. locking this thread, I'm quite happy with bug reports in the other thread"
Sorry, didn't mean to step on your toes! :-)

Using the center key to change the Brgt setting seems to make the key act a little quirky.

In Default I have 2/Cntr/Brgt/Set/255

1. When using the center key to select an item in a "find list" it is jumping back to the first item in the list everytime.
2. When trying to select a default button I have to press the center key multiple times to get it to work, still doesn't work most of the time.

Thanks,
Don

So I switched it to NavU and now that button is not working correctly neither is the Cntr button. If I hold down Cntr I get a dialog box that says "!1". NavU will work to move up only 1 spot and then it doesn't do anything else.

I tried deleting Aptdb and starting from scratch that didn't help.

Edit: I just caught that I had the Cntr key assigned like this 2/Cntr/Apt/Call/1
After removing this the center key is working correctly for selection.
Anyway for some reason assigning the Cntr key makes it unusable for anything else.

HTH,
Don

Last edited on 19 Aug 2008 12:51 by donl517 Show more

Re: Apt 1.3b1

Pent 03 Sep 2008 09:01

That's an old one. I thought it was on the bugs/limitation list already, I added it back.

Edit: the NavU is a new one, and I can't replicate it. Anyone else ?

Pent

Last edited on 03 Sep 2008 09:05 by Pent Show more

Re: Apt 1.3b1

donl517 18 Aug 2008 14:30

Back to the Brgt setting:

"This is what I use on the Tx to keep brightness when setting with the system brightness popup:

19500/FExit/Brgt/Copy"

What is 19500? Is that the form ID?
When I go to the preferences panel and the power setting screen, where the bright control is, it says for Lst form: "Preferences: 1000"
This string is too long to fit in the form ID field.

Thanks,
Don

Edit: I think I have this figured out and working now.

Bug: After using Apt to change the brightness the keypad is not always shutting off.
Edit: Ah I just noticed the screen is still on as well, you just can't tell because the backlight is so low.
Strange most of the time 45 is more the adequate light and other times it is not. When I checked Apt's
Default it was at 45 but I couldn't see the screen. Every other time it was fine. Yeah the backlight is
acting really weird now even with Apt disabled. Any Thoughts?

These are my settings:

Buttons:
2/Cntr/Brgt/255
Events:
20/Idle/Brgt/Set/45
19500/FExit/Brgt/Copy

It's not changing the default setting in either case. I'm guessing it must be the form ID.

I set up a tag to do:
1/Tag/Brgt/Copy

Changed macros to:
Buttons:
2/Cntr/Brgt/255
&/Apt/Call/1
Events:
20/Idle/Brgt/Set/45
&/Apt/Call/1

This works.

I'm guessing FExit didn't work because of the Form ID.

Don

Last edited on 19 Aug 2008 21:37 by donl517 Show more

Re: Apt 1.3b1

technical1 18 Aug 2008 19:48

Pent,

Excellent job on the oHrd press 'n hold. Works like a charm on my Centro.

Good news, bad news on the locking feature & the bad news isn't all that bad.

Full screen locking seems to work - good news, but the bad news is it needs some polishing.

The dialog to let you know that the specified amt of time (2 seconds) have passed does NOT come up. It even lead to the following situation:

Full lock set for 1 sec, w/Cntr as the trigger (F 1 Cntr) I unknowingly held for 3 or 4 seconds, cause I didn't see the dialog pop up & got a crash/reset. This has been reproduced on my Centro. If I have F 2 Cntr & hold it for 1 sec & release, I get the expected x, but if I hold it for the prescribed 2, it opens, but no dialog to warn me to let go now. Holding for 4 seconds causes crash….

Partial locks work & do show a " - " when the prescribed time period is reached.

A quirk, I tried to lock Agendus, which I have both an icon for & a native buttons pref setting for Centro Hrd2.

The lock works for when I tap on my launcher's Agendus icon (Initiate) & does not work when I press on Hrd2…. Agendus just comes up unhindered by any sign of locking.

BTW, see if you can get a lite version for 1.3 out there…..

I put up an announcement about the new Treo oriented features on MTDN & quoted donl517 fm 1src's announcement, & I pushed the capabilities of oHrd 1-4 for 0,1,2, or 3 seconds & gave some more info about the compatability issue i.e. needing a ver 1.2 AptDB & the Apt-Assist & GetCoord & Khroma files… but I now see that nobody's gonna be able to test it. Knowing the secret directory, I just d/l'ed the 1.3 b1 beta, not knowing there is no 1.3 Lite version….

So if you can, please get a lite version out there…. It will help get more sales based on interest in new Treo features….

All the best,

technical1

Re: Apt 1.3b1

donl517 19 Aug 2008 12:29

I haven't been around Apt as long as some so maybe this has been asked and answered but;
Is there a reason we only have 10 lines for a macro on a page? Can this be increased?

The main place I'm running into space problems is in the Defaults settings.

Also, there is one button on the Treo that is not being utilized, unless I'm missing it in the list.
Opposite the Red Power button is a green button, can that be added to the list?

Thanks,
Don

Last edited on 19 Aug 2008 12:33 by donl517 Show more

Re: Apt 1.3b1

Anonymous (195.137.114.x) 19 Aug 2008 12:41

Don

The real limit is 17.

To get 17 on a Treo, use the Toggle Font option in the top line menu. It gets quite small, but the lower lines are retained when you switch back :-)

ChasTreo

Re: Apt 1.3b1

donl517 19 Aug 2008 13:00

Ah thanks for the info ChasTreo, I saw that but never tried it to see what it was about.

Just thinking out loud, would it be possible to add pages/screens to this?
Maybe it is not even necessary, haven't thought about the next use of Apt yet for my treo
but with so many possibilities my brain is spinning. ;-)

Don

Re: Apt 1.3b1

Anonymous (172.163.36.x) 19 Aug 2008 16:47

Don,

Say you have a macro that will take up 3 lines & you just don't want to use that much real estate in Apt, not to worry.

You can put them in the *Tag#* section & call them, like a batch file fm one line in the main screen… very empowering….

An example: I have 1 Hrd3 Fill Fave translated fm Apt into English that is a 1 second press on the 3rd hardkey & the action taken is to Fill the results of the tag called Fave, which is in *Tags1* (which is just below *default*) & the following is there in the *tags1* screen:

(f) Tag Fill Fave1 -> (f) represents fave, the tag name, action is to fill the set of favorite apps list in the set of faves - Fave1

• Fill Rcnt 4 -> The asterisk means you will get a popup menu, Fill(ed) by Recent apps & it will show up to 4 of them…

btw, the limit of lines is 14 when you 'toggle fonts' fm the menu, at least on my Centro it is…

Good luck, technical1

Re: Apt 1.3b1

donl517 19 Aug 2008 12:54

In the buttons menu if I try to change a button assignment i.e. Cntr to Side
It is pushing the Cntr assignment to the line below it instead of replacing it.

It is also doing the same thing in the Events page with the time feature.
Tried moving my timed events to the bottom of the Toggle Fonts page and
it was going haywire with times and trying to cancel/replace them. The only
time it will let you get rid of them is if they are the last item in a macro set.

Thanks,
Don

Last edited on 19 Aug 2008 16:02 by donl517 Show more

Re: Apt 1.3b1

Anonymous (172.163.36.x) 19 Aug 2008 16:51

Don,

Hi again, t1 here.

It is not happening like that on my Centro (which device do you have?), so it sounds like the AptDB may have become corrupt.
Write down all of your settings - I know - but what can you do? & delete the AptDB file & recreate by hand…. This has helped me b4….

Good luck,

technical1

Re: Apt 1.3b1

donl517 19 Aug 2008 16:06

The whole screen is not being refreshed when changing/deleting entries.

Thanks,
Don

Re: Apt 1.3b1

Anonymous (172.163.36.x) 19 Aug 2008 16:59

Don, I'm guessing you are trying to delete an empty profile, fm which you've deleted Apt settings. Go to the Profiles menu heading & delete fm there. You'll know it works when you automagically are looking at the *default* profile….

t1

Re: Apt 1.3b1

donl517 19 Aug 2008 18:08

No I was trying to rearrange some stuff so it was more logical. When I cleared a row there were some left over pixels that didn't get refreshed.
"ghosts" if you get my meaning. ;-)

Don

Re: Apt 1.3b1

Anonymous (172.164.199.x) 20 Aug 2008 04:07

What device are you using & how much cache do you typically have?

You did upgrade fm 1.2 to 1.3b1, didn't you? Maybe you would like to try to go back to 1.2 & do your AptDB for that by hand, & then upgrade… just to rule out any AptDB probs that might have been hiding in wait, underneath the 1.2 version…

Also, if you have a reliable backup, like NVBackup, you might consider wiping out everything & installing Apt 1.3 as 1st app, on the newly clean device, put the environmental stuff into Apt & after restoring the rest making the rest of the Apt settings….

Otherwise, we're gonna have to wait until Pent gets back online…& bring his programming chops to bear on your issues. I'm just trying to do standard isolating stuff, hoping it helps…

technical1

Re: Apt 1.3b1

Anonymous (172.164.199.x) 20 Aug 2008 04:12

it's me, t1 again.

There have prev been issues w/artifacts remaining. Try going fm Buttons scrn to Events & back & see if it doesn't clean up the junk pixels hanging out.

About settings in line 3 being pushed down to line 4, there have been internal rules about what can be put into a line, so it doesn't conflict w/other lines i.e. if you have 1 Hrd 3 etc, then in following lines, the 1 option wouldn't be available for Hrd 3….

Having said that, I found that in some cases I was allowed to do just that… hear that Pent…?

All the best,

technical1

Re: Apt 1.3b1

donl517 20 Aug 2008 12:06

T1,

My device is a Treo 755P.
I usually have over 11,000,000 of cache free.
V1.2 is the first version I tried, so yes I did upgrade from 1.2.

I don't have time to try wiping it today, maybe tomorrow.

Changing screens button/events didn't help refresh the screen. It finally cleared up after I went to enough different screens that it had redrawn all the pixels.

The settings being pushed down: What I'm trying to get across is, I was only trying to change the assigned button. (i.e. Cntr to Side) Cntr was not called anywhere else. When I select the button assignment, scroll down and click side; it is pushing Cntr to the line below instead of replacing it.

HTH,
Don

Edit: Having said all that I can't reproduce the problem so it may be a non issue.

However I can reproduce this everytime: (Edit: I could until I posted I could, Stupid Bugs!!) ;-)
Toggle Fonts, Toggle back; The name in the drop down list at the top is truncated until you select something else.

Last edited on 20 Aug 2008 12:18 by donl517 Show more

Re: Apt 1.3b1

donl517 20 Aug 2008 19:23

Aha, got it.

Apt>Default>Toggle Font>Tags 1>Default>Toggle Font.

Launch Apt go to default buttons, toggle fonts, change to Tags1, change back to default & toggle fonts

Default does not refresh correctly.

HTH,
Don

Re: Apt 1.3b1

cmlx 20 Aug 2008 10:58

Very good, it seems that 1.3b1 solves the auto-disable problem on my treo 650.

Re: Apt 1.3b1

donl517 20 Aug 2008 13:16

When using the High or Very High priority setting Apt is keeping some programs from having any control over button presses.

I'm using Butler, Phone Technician & Reset Doctor from Hobbyist Software.
They all have a Close button on the main program screen, these simulate a HK4 key press.
They do not work with anything above the normal setting.

I realize this is pretty much the whole point of the priority setting; however I don't have anything assigned to HK4 in Apt.

Thanks,
Don

Re: Apt 1.3b1

Anonymous (172.131.7.x) 20 Aug 2008 16:11

Had the same problem, but didn't get Hrd 4-like results. You could just ignore the non-working Close dialog button issue & go on to other apps simply by pressing other hard buttons…. or Apt trigger buttons, or you could go to Butler, etc. & in the Prefs+ screen just disable triggers for the app(s) in question (need to visit the other app screens for ea. disabling).

HTH, technical1

Re: Apt 1.3b1

Anonymous (172.131.7.x) 20 Aug 2008 16:21

BTW, I just tried to recreate your Hrd4 behavior & couldn't. It could be that your AptDB has probs i.e. is corrupt…

the answer for that is to copy all of your settings (I got into the habit of having a MasterList on paper for this, yup, still use that stuff!) & delete your AptDB file & recreate by hand. Can be tedious, but it does help isolate & since I couldn't recreate it w/the same Apt / Butler settings…. Good luck, technical1

Re: Apt 1.3b1

donl517 20 Aug 2008 19:18

It is very easy to reproduce on the Treo 755P. I had forgotten about the default button setting in the Apt installation: 2/Hrd4/Apt/Menu
If I delete that line the close button in the other programs works. FYI I tried this with a new Aptdb and had the same effect.

Like I said I understand this is what the priority setting is for; In my mind this is a little buggy.
Just passing along the info.

Thanks,
Don

Re: Apt 1.3b1

Anonymous (172.168.16.x) 21 Aug 2008 06:03

Don, Good job on finding that 1 Hrd4 Apt Menu was behind what was affecting the Butler (et. al.) Close button (rather than some sort of unknown issue 'just lurking around somewhere'.

Hopefully Pent can address this on a deeper level, once he's past his AFK time. What about re-assigning it to another Hrd button besides 4? Just in case it is some limited amount of 'stepping on' memory address 'toes' going on here…

Don't know what prompted your comment about knowing what the priority setting is for… never doubted you…

Certainly there is something going on that is less than optimal, but the workaround of disabling triggers (Prefs+ screen) for the apps in question seems reasonable… that's what the feature is for… technical1

Re: Apt 1.3b1

donl517 21 Aug 2008 12:32

It is certainly not a deal breaker, by any stretch of the imagination. I can get by with pressing one of the hard keys to exit.

Thanks,
Don

Re: Apt 1.3b1

Pent 03 Sep 2008 09:12

You could try assigning a null action to hrd4 in just the profiles of the apps with problems.

0/Hrd4/-

I realise that's bug avoidance :-)

Pent

Re: Apt 1.3b1

SportyRydr 20 Aug 2008 18:27

Back to the disabling thing again. :u|

I hadn't had it happen once since 1.3b1…until last night. I have mobileClock launching itself at 12:01a, so mobileClock can be running when it's time for Apt to launch a mobileClock-specific macro. So, last night, I was doing something on my Treo, and then turned it off when I was finished. Well, the instant I turned it off, it came back on at 12:01 when mobileClock launched itself. I mean, it came back on so fast that the keyboard lights didn't even come back on. Anyway, at that point, Apt was disabled. The Squeal values are:

Menu: 0
Macro: 0
Trig: 2642190
StepNo: 1112300085
NoSteps: 1397510996
WTicks: 0
AppL: 2499835
Deg:0
Prefs: 0
Power: 0
Lock: 0

Thanks,
SportyRydr

Re: Apt 1.3b1

Pent 03 Sep 2008 10:39

Did you install the new squeak (I put one up that goes with 1.3b1) ?

Those values are crazy :-)

Pent

Re: Apt 1.3b1

donl517 21 Aug 2008 14:41

Tags or macros seem a little quirky; I tried setting up a couple of DA's using Accessorizer, they seem to work fine.
When I call them as a tag the first one called, and it doesn't matter which one it is, the screen flickers
4 times than executes the next step and than I get an Apt error message about a missing object and it
continues on and finishes the macro.

It acts like it is calling the DA 4 times. Below is the setup. I tried different variations of this, including
1 line in buttons on default and one long macro for each in tags.

Thanks,
Don

Tags1 Screen 3
flf/tag/DA/FastlaunchDA
&/Ctrl/Tap/1004
&/Hard/4
kcn/tag/DA/KeyCaps600DA
&/Ctrl/Tap/1001
&/Hard/4
kcf/tag/DA/KeyCaps600DA
&/Ctrl/Tap/1002
&/Hard/4
fln/Tag/DA/FastlaunchDA
&/Ctrl/Tap/1003
&/Hard/4

Default
Buttons
2/Hrd2/Apt/Call/flf
&/apt/Call/kcn
3/Hrd2/Apt/Call/kcf
&/Apt/Call/fln

Re: Apt 1.3b1

Anonymous (172.168.16.x) 21 Aug 2008 14:51

Don, I'm using *tag1* for the very simple call to a macro that runs a popup w/my faves & recent…. only thing that comes to mind is that you should try this w/a DA that was written as a DA to begin with… Alex mentioned that he can't guarantee that all apps will become DAs successfully… this way, if it still happens when natively written DAs cause this, then we'll have to wait for someone w/programming experience… you'll still have your issues w/the Accessorized DAs you wanna use, but at least you'll know if Apt is the root cause of this or not….

Hopefully Pent will be able to shed light on this…

Good luck, HTH, technical1

Re: Apt 1.3b1

donl517 21 Aug 2008 16:35

T1,

I read Alex's description of Accessorizer when I downloaded it, so I'm aware of the potential for a program not to work.

However, both of these are working as DA's when launched with Apt independant of a macro. The problem occurs only when running
them within a macro. Then it only occurs if they are the very first DA launched. If either one of them are the second DA launched
they work fine. (there are no screen flickers, no errors, etc.)

I should stress that even with the error the macro completes and the actions are completed. If I check either program after I run the
macro they are in the state (on/off) that they are supposed to be in.

Thanks,
Don

Re: Apt 1.3b1

technical1 22 Aug 2008 06:06

Don, you clearly know your way around a Palm pda…

I wanted to suggest a possible influence. Based on what you wrote, it does seem that Apt has a kink or two in this scenario; esp since both otherwise work & only when either is in the 2nd position does the prob creep up… I thought that maybe a DA that was created to begin with as a DA might have bearing on this issue, as compared to regular apps that have been accessorized - hey it was worth a shot…

However, in other instances of unexpected influence, I have found a good & viable work-around, in my own opinion:

the prob w/Butler's Close button not working when Apt Menu trigger is associated by default w/Hrd4. What I said b4 about ignoring it unless you really need to be in the prev app, is at best a band-aid solution for a big bruise - Apt shouldn't prevent other apps fm working, albeit in an all but innocuous manner; disabling the Triggers feature in Apt is a bit more elegant; but more direct is something I just discovere: changing the trigger assignment fm the default of
1 Hrd4 Apt Menu, in my case to 2 Hrd2 etc, …. & there are no probs whatsoever. Therefore it is an issue w/which apps & calls to resources play nicely w/each other & which don't.

Of course, the best would be to contact Rob at HobbyistSW, which I intend to do & hopefully he will be able to shed some light on the meaning of the diff scenarios mentioned above & he can either do some sort of patch/fix for Butler, or suggest something for Pent to look into….

Hope this helps, technical1

Last edited on 22 Aug 2008 06:16 by technical1 Show more

Re: Apt 1.3b1

donl517 22 Aug 2008 11:13

Hey T1,

Thanks for the post.

I had thought about the button reassignment as well. Moving it to another button would be fine. I really don't need either function on a daily basis. (i.e Apt Menu, Butler Close)
However, who knows how it might effect something else down the road. It could potentially cripple another app.

On a couple of occasions I've posted bugs and within just a short while Pent has come back with "That is fixed now". I just wanted to give him a chance to work his magic. ;-)

Maybe there isn't a clear solution to the problem, and that is fine, but he may look at it and go "DOH!! I can't do that" and the bug goes away. :-)

Thanks,
Don

Re: Apt 1.3b1

technical1 22 Aug 2008 13:43

Don,

Glad to be part of the process. I agree about how changing a conflicting setting can save probs down the road, I didn't take that into consideration….. but something you should take into consideration… Pent seems to still be AFK… It is harder to work magic if you don't know what to work it on… t1

page 1 of 212next »