Help, XP Pro administrator account serious difficulty

[JamesC]

Thanks Collin,

Here are a few more details about asus probe to give you more of an idea,
Location: C:\Program Files\ASUS\Probe

It loads up (or tries to) when a user account is opened. If the account is an administrative account there is no problem it just loads up. If how ever a lower user account is started the error messages that i have described earlier appear:

Title is always the same - AsmiHwIo
Then these error messages occur one after the other
- cant open service control manager
- cant create driver service
- cant open driver service
- cant open AsmiHwIl.dll

Now really i am going to be the only one who finds the information that pc probe offers interesting so i wouldnt be bothered if it didnt run in any of the lower user accounts at all.

As it starts up i would have thought it would be in the startup folder in the start menu, however the only things that are in there are 'Getright' and 'Office'.

I went into the file C:\Program Files\ASUS\Probe to see if i could just adjust the way the program runs, but obviously as there is no target line there is no way i could do that.

What are your thoughts about this,
thanks
James

 

[c0rv1d43]

Here are a few more details about asus probe to give you more of an idea,
Location: C:\Program Files\ASUS\Probe

It loads up (or tries to) when a user account is opened. If the account is an administrative account there is no problem it just loads up. If how ever a lower user account is started the error messages that i have described earlier appear:

Title is always the same - AsmiHwIo
Then these error messages occur one after the other
- cant open service control manager
- cant create driver service
- cant open driver service
- cant open AsmiHwIl.dll

Yes, those are the sorts of messages you'd expect to see when the system is receiving instructions to start processes that can't be run by the current user.

Now really i am going to be the only one who finds the information that pc probe offers interesting so i wouldnt be bothered if it didnt run in any of the lower user accounts at all.

If you decide to not use the program for lower level users you could just have them ignore the messages. They shouldn't cause any harm to the system. However, if you wish to get rid of the messages OR if you wish to have the program available for use by the non-administrative users you're going to have to do some digging.

As it starts up i would have thought it would be in the startup folder in the start menu, however the only things that are in there are 'Getright' and 'Office'.

I went into the file C:\Program Files\ASUS\Probe to see if i could just adjust the way the program runs, but obviously as there is no target line there is no way i could do that.

Yes, there are other places than the startup folder from which a process can be launched at startup. We're going to need to get some information before we can try to figure out how to alter the system to suit you. First of all you should go to the Start|Run dialog and type in "msconfig" (no quotes) and hit the <Enter> key. You're going to want to look on the Services tab of that applet. Notice the little checkbox down at the bottom beside the words "Hide All Microsoft Services"? Place a checkmark in there so that we can get a manageable list. I'd like for you to include that list of non-Microsoft services when you reply to me. Also, I need for you to look at the Startup tab in MSCONFIG. This is where you can find the locations of the instructions that cause non-service startup processes (and even some special types of services) to be started when the machine is booted. We need this list, too. Please note that we need the complete list, including all information in the Startup Item, Command, and Location columns of that window.

You'll notice that some of the items are in locations like "HKLM\SOFTWARE\Microsoft\Windows\CurrentVersion\Run" or "HKCU\SOFTWARE\Microsoft\Windows\CurrentVersion\Run". Those refer to locations in your registry in the HKEY_Local_Machine and HKEY_Current_User hives. I suspect that this is the locations from which your Asus PC program components are loading. In order to fix your problem we'll either have to directly edit the startup commands in the registry or we'll have to make use of the Startup Control Panel utility I mentioned in a previous message in this thread.

BTW, I hope you had a good time at your graduation. Again, you have my congratulations.

- Collin

 

[JamesC]

Hi Collin,
Thanks alot for your congratulations, I did have a very good time. It was nice to celebrate with friends after 3 years hardwork. Sorry it has taken me a few days to reply but I have been busy laying down a wooden floor and building some stone steps at my gilfriends parents house. I have the list for you, and i am afraid it is a long one, so here goes:

SERVICES
Norton antivirus auto protect service Symantec corp
Scriptblocking service " "

STARTUP
igfxtray c:windows\system32\igfxtray.exe HKLM\SOFTWARE\MICROSOFT\Windows\CurrentVersion\Run
hkcmd c:windows\system32\hkcmd.exe "
Mixer Mixer.exe/startup "
Asusprob c:\Program Files\Asus\Probe|Asusprob.exe "
navapw32 c:\PROGRA~\NORTON~1\navapw32.exe "
hpztsb04 c:\Windows\System32\spool\drivers\w32x86\hpztsb04.exe "
Agent c:\Program Files\Cyberlink\PowerVCRII\Agent.exe "
ctfmon c:\Windows\System32\ctfmon.exe HKCU\SOFTWARE\MICROSOFT\Windows\CurrentVersion\Run
msmsgs "c:\Program Files\Messenger\msmsgs.exe"/background HKCU\SOFTWARE\MICROSOFT\Windows\CurrentVersion\Run
GetRight - Tray Icon c:\PROGRA~1Getright/getright.exe Common startup
Microsoft Office c:\PROGRA~\MICROSOFT~4\Office\OSA9.EXE- b -1 Common startup

Sorry again it took me so long to reply, there just isnt enough hours in the day! Just one other thing, i am selling my old computer and want to format it and reinstal the operating system (Windows ME), how should i go about this. Is there a way of making sure none of the data can be recovered???
Thanks James

 

[JamesC]

Sorry think the above message might be a bit confusing, i put spaces in but they were removed when i submitted the message. Where i have put " this means that the Location is the same i.e HKLM\SOFTWARE\MICROSOFT\Windows\CurrentVersion\Run, apart from messenger which has " in the name.

Thanks again
James

 

[c0rv1d43]

Hi, James.

I've been out of the loop for a couple of days. I didn't realize you had responded back to the thread. I'm sorry for the delay.

At the moment I'm on top of something, so can't give as much time to this as I'd like -- until a little later today, perhaps.

I have a couple of preliminary questions. Have you decided what you wish to do about the Asus Probe software -- do you wish to have it run only for admin users, or do you wish for it to run for everyone? The other question follows from the information you provided. I see the command name (and where the executable itself resides) from your message, but I don't see the location of the "call" for it. If MSCONFIG doesn't show anything in the location column for that executable you may have to use the previously mentioned utility (Startup Control Panel) to find out how the executable is being called or started. Or you can just roam about through the various possible culprits. It could be started from the registry, but, if so, that should be shown in the location column of the MSCONFIG utility. It could be started from a script. Do you have any startup scripts running? If it were in a Common Startup folder or a Startup folder, it should show, also. Anyway, we need to know WHERE it's being started from so that we can take the appropriate action to get the result you desire.

As far as preparing your PC for sale is concerned, this freeware utility from SysInternals is probably your best bet. You can just put it on a WinME boot diskette, boot from the diskette, and have at it. You can set it up to run all night, and the next day you're ready to boot from the WinME setup CD and re-install the OS. No one, short of someone with serious data recovery resources, would stand a chance of recovering much or any of your old data after that.

I'll be back as soon as I get a chance.

- Collin

 

[JamesC]

Hi Collin

Under the location heading of the startup tab of msconfig it lists HKLM\SOFTWARE\Microsoft\Windows\CurrentVersion\Run is this the location of the "call". In answer to your question of whether i want to deactivate or set asus probe up to run for lower level accounts I am not really that bothered - whatever is the easiest i think. The only advantage of having asus probe active on the lower user accounts is that it sounds an alarm if the system overheats and the user would know to turn the computer off. To be honest however i am not really that bothered and if it would be a lot easier to deactivate it on the lower accounts that would be fine. I am the only person that will be bothered by system temps. On the other hand it would probably be useful for me to know how to make it run in case i run into a similar problem with another piece of software.

With the data wiping program should i use it before or after i fdisk or even instead of formatting?

One final question to pick your brain, my cd writer recently died on me, the program i used to record was ce quadrat. a fair few of my discs only had closed sessions and were not fully closed disks. When i chose this option a message used to come up saying that the disk would only be readable in "this" drive until the disk was fully closed. Do you know whether when i get my new cd writer it will be able to read the disks that only have closed sessions not fully closed disks. is it drive dependant, software dependant or neither and any unclosed disk will be able to be read in any cdwriter?

Thanks a lot for all your help (i know it sounds a bit like a broken record me saying this all the time but i really do mean it)
James

 

[c0rv1d43]

Originally posted by: JamesC
Hi Collin

Under the location heading of the startup tab of msconfig it lists HKLM\SOFTWARE\Microsoft\Windows\CurrentVersion\Run is this the location of the "call". In answer to your question of whether i want to deactivate or set asus probe up to run for lower level accounts I am not really that bothered - whatever is the easiest i think. The only advantage of having asus probe active on the lower user accounts is that it sounds an alarm if the system overheats and the user would know to turn the computer off. To be honest however i am not really that bothered and if it would be a lot easier to deactivate it on the lower accounts that would be fine. I am the only person that will be bothered by system temps. On the other hand it would probably be useful for me to know how to make it run in case i run into a similar problem with another piece of software.

I'm just on my way out the door. We can almost certainly find a way to get the app to run properly regardless of who logs in, but I don't want to try to tackle registry editing options until until I have a bit of time. I should be back this afternoon / evening with time enough to write the explanation carefully. I don't want to "help" you make things worse.

With the data wiping program should i use it before or after i fdisk or even instead of formatting?

It doesn't really matter. It will only write to an established file system, AFAIK, but whether you fdisk and format first and then use it OR use it and then fdisk and format OR just use it and don't bother with fdisking and formatting is essentially immaterial. Just read the instructions on the download page at SysInternals to use it to best effect.

One final question to pick your brain, my cd writer recently died on me, the program i used to record was ce quadrat. a fair few of my discs only had closed sessions and were not fully closed disks. When i chose this option a message used to come up saying that the disk would only be readable in "this" drive until the disk was fully closed. Do you know whether when i get my new cd writer it will be able to read the disks that only have closed sessions not fully closed disks. is it drive dependant, software dependant or neither and any unclosed disk will be able to be read in any cdwriter?

I'm not familiar with that program. Did it's message actually specify THIS CD drive, or do you think the message was more along the lines of "This disk may not be readable in other CD writers? Most CD writing software capable of writing multi-session CDs will warn you that CDs left open may not be readable in SOME other CD writiers. But those CDs will usually be readable in most recent CD ROM drives running under most recent operating systems. They may not work on older CD ROMs or in standalone players. I suspect that's what the warning was about, but I can't be sure. Can you just try them in another machine nearby to see?

Wifey is giving me "the look", so must sign off. Going a couple of hours away to do some visiting. I'll be back to try to do a careful outline of your options on dealing with Asus PC Probe. It's not rocket science, but I just don't want to type a dumb instruction that racks up your system.

- Collin

 

[c0rv1d43]

So, according to information posted previously, we have --

Asusprob c:\Program Files\Asus\Probe|Asusprob.exe

being started from the registry location mentioned in this paragraph --

Under the location heading of the startup tab of msconfig it lists HKLM\SOFTWARE\Microsoft\Windows\CurrentVersion\Run is this the location of the "call". In answer to your question of whether i want to deactivate or set asus probe up to run for lower level accounts I am not really that bothered - whatever is the easiest i think. The only advantage of having asus probe active on the lower user accounts is that it sounds an alarm if the system overheats and the user would know to turn the computer off. To be honest however i am not really that bothered and if it would be a lot easier to deactivate it on the lower accounts that would be fine. I am the only person that will be bothered by system temps. On the other hand it would probably be useful for me to know how to make it run in case i run into a similar problem with another piece of software.

From what you've said it sounds as though the program is allowed to interact with the desktop, and that this is what is causing problems when a non-admin user is logged in. I wish I knew more about the program. And I'd really suggest that you ask the vendor for help with this since they should know very well exactly how to address this issue.

If you want to investigate on your own then the first thing I'd suggest is to crank up Task Manager while logged in as a non-admin user and take a look in the Processes tab's window. Look for asusprob.exe in the Image Name column of that window. Check out the assignment under which it is operating in the User Name column. If it is SYSTEM, then there's a problem with the desktop interaction of the program that causes non-admin users to have problems with it. If the User Name is listed as the non-admin user, then the registry entry that starts the program might be edited to start the program with different credentials.

Please let me know what you find, and maybe we'll be able to find a solution. We can also hope that someone who knows what s/he's actually doing will show up to help us out!

I am NOT an IT guy. I'm just a physicist. And a retired (and probably senile) one at that. Yeah, yeah. Everybody tells me that I'm not senile. But they're probably just humoring me.

- Collin

 

[c0rv1d43]

Duplicate Post! Weird! I did NOT hit the button twice!

 

[JamesC]

No problem, I know that kind of look and thats not something to be messed with. Apologise to your wife for me for taking up so much of your time.
I think you are right about the cd burner, that is what i suspected. I reckon that if i use the new cd burner with the old software i should be ok. i can then close all the disks and upgrade to Nero burn which i have heard is the best software.

Take care Collin, hope you had a good time on your visit,
James

 

[c0rv1d43]

Do let me know what you find out. I'm still going to be here to try to help out. Maybe we'll both learn something!

I'll probably not be getting back online before tomorrow morning.

- Collin

 

[JamesC]

Hi Collin,
I looked under task manager. While asus probe is trying to start up it is listed under the user name, once it fails to start up it is not listed in task manager.

Hope your visits went well . Its 00.30 am here and i am going to bed now, my girlfriend Zoe was wondering where abouts you are based. I am at her house at the moment in Oxfordshire, UK.

James

 

[c0rv1d43]

Hi, JamesC.

I'm back. All rested and refreshed and ready to come as close to not misinforming you as is within my power to be.

I've come up with a little procedure for you to try, and I've tested this on my system with every single non-service startup process I have on my notebook. The procedure works on all of them, so I feel reasonably confident it will work for you, too.

But first we need to be sure about a couple of things, and we should take at least one precautionary step -- just in case.

First of all I just noticed something higher up in the thread. When you notified me of the list of startup processes, I identified this one

Asusprob c:\Program Files\Asus\Probe|Asusprob.exe

as the "culprit" process. I just now noticed that there is a "|" symbol sitting between the words "Probe" and "Asusprob.exe". Is that actually what MSCONFIG shows for in its STARTUP tab? That symbol is the symbol for pipelining, and I think that it's probably just supposed to be a "\" (backslash) instead. But if it IS actually a pipeline symbol then I'm not sure we should try the procedure I'm going to outline. I'm not saying that it wouldn't still work, but I just have no experience with the use of that feature from within a registry startup call. I don't know if there are special conditions which apply or not.

The precautionary step you need to take is to create a System Restore Point. Go into your Control Panel, switch it to Category View if it isn't already in that format, click on the Performance and Maintenance link, then click on the System Restore link in the upper left-hand corner of the window. You'll be presented with the System Restore dialog. Click on the "Create a restore point" radio button, and click on the Next button at the bottom of the dialog. On the next page type in a descriptive name for the restore point you'll be creating. Then click on the Create bottom of that page. Give the system time to do it's thing, and then OK and close your way out of the dialogs. If things go really wrong (and they almost certainly won't) with the registry edit, you should be able to boot into Safe Mode by hitting the F8 button immediately after the Power On Self Test. You'll then be able to go into the same System Restore applet and choose to restore the system to an earlier point, at which time you'll choose the restore point you just created.

Now for the procedure. Not rocket science by any means, but DO be EXACT. The registry is no place to make typographical errors!!!

Make sure that you are logged in as an admin user. Hold down the Windows key and hit the letter "R". The Run dialog should appear. Just type "regedit" (no quotes) in the field, and hit the Enter key. A window called Registry Editor should appear. You need to drill down to the point indicated in your earlier message. (It's just like a directory structure in Explorer.) Notice that "HKLM" stands for "HKEY_LOCAL_MACHINE", so this --

HKLM\SOFTWARE\Microsoft\Windows\CurrentVersion\Run

will actually be at this location --

HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\Windows\CurrentVersion\Run

At that location in the registry you'll look in the right-hand pane of the Registry Editor. Locate the item named "Asusprob" (Asusprobe?). Right-click on it, and choose Modify from the context menu. You should see a little two-field dialog appear. It will contain the fields Value_name and Value_data. You're going to modify the Value_data from this --

"C:\Program Files\Asus\Probe\Asusprob.exe"

(and it DOES include the quotes this time) to this --

runas /savecred /user:AdminUserName "C:\Program Files\Asus\Probe\Asusprob.exe"

You will be replacing the term AdminUserName with the name of an actual full administrative user of the machine. Click the OK button to close the Edit String dialog, the click on the close button of the Registry Editor to close it. On the next reboot, just after logging in (as one of the users with the problematic Asus Probe behavior), you should see a CMD (C:\ icon) window pop up. Depending upon whether or not the credentials for the admin user you chose to use are already cached, that box may prompt you for that admin user's password. After that, first time I think you shouldn't be prompted for the password again. Do go through a reboot / logon for each of the non-admin users so that, if the password has to be entered in each of them, you get past that hurdle for those end users. After you're up on the desktop with the OS fully loaded and the boot time hard drive activity finished, crank up Task Manager and look on the Processes tab for "Asusprob". You should see the admin user listed as the user of the process, even though you're actually logged on to the system under a non-admin user's credentials.

REMEMBER that I'm not so sure about that pipeline symbol. If it really is there, then I'm not certain just what ramifications that might have, if any.

ALSO REMEMBER that computers are literal beasts, as you've probably surmised during this little adventure. That runas line I typed above is, with the sole exception of the "AdminUserName" item, EXACTLY what you need to place in that field. (That's assuming that my surmise about "|" really being a "\" is correct AND that the original command line you gave me has no other typos in it.)

If you have any questions, ask them BEFORE proceeding. I don't wish to help you get into trouble. I did test this method as thoroughly as possible, considering that I don't have access to your system, or even to the executable we're trying to work with.

I'll hope to hear good news.

- Collin

PS: I live in the GMT - 5:00 zone. The daytime difference certainly contributes to the delays experienced in this message thread, doesn't it?

 

[JamesC]

Well what can i say, it worked first time, no problems at all - great .
Call me fussy but i like to have everything working just perfectly and it really iritates me if something is not working quite right so thanks a lot for all your help. I have fiddled with the registry a fair bit with Millenium so it hardly took any time at all to sort out. I did find another program that wasnt working properly under the other acocunts and that is PowerVCRII but as it was not much good (its an old version) i just deleted. I am fairly sure that had i wanted it to run the process would have been exactly the same and i would have been able to deal with it myself.

One more quick question. Ever since i upgraded to XP my modem has been really unreliable. I could only find connexent and generic drivers for it - what does this mean? I am fairly sure i will have to buy a new modem anyway.

Thanks again
James

 

[c0rv1d43]

Do you happen to know the exact name and model of your modem? I'm assuming it's internal. Those can be hard to tell. If you can get an FCC Ident. # off of the card it can be looked up on an online database. The idea is to find out the exact make / model and then to see if WHQL certified drivers are available for it. If not, and if other drivers don't seem to make it function properly, then you'll need to get a replacement. Modems are cheap enough these days. I accept the internal ones that come mounted in the various systems I buy, but my preference is for external ones -- WinXP certified ones, of course. U.S. Robotics makes some outstanding ones. They offload a lot of the processing from the CPU. That's always a good thing, but it's especially advantageous on systems that are a bit lacking in horsepower.

If your modem doesn't behave properly, and you can't get better drivers for it, just replace it. When I install WinXP on most systems, even some older ones, the result is almost like seeing a total hardware upgrade. Every device (the ones with decent drivers, that is) behaves like an improved piece of hardware. There's no reason to use WinXP with faulty drivers and / or hardware. Those are WinXP's only real bane. It's a fantastic OS when the hardware is working properly, but a real hassle when it's not.

I'm delighted that we got your system to behave itself. I enjoyed trying to help you figure this stuff out.

Best regards,
Collin

 

[JamesC]

I am glad you enjoyed it, i did too. I like fixing problems (even if you did do all the real work!!!).
The modem is an Aztech MDP 3858SP - WE Data Fax Modem. When i loaded XP it installed it automatically from its driver database - no need to put a disk in or anything. When i was dissapointed by the performance i tried the drivers on the website but they are no better. The speed it shows me is 37.2 Kbps, under ME it showed 48000bps. it is really unreliable to connect and sites (like this page) just take an age to load. looking under task manager it seems as if it only ever hits about 50% under the networking tab. Also when windows tries to automatically update it never seems to properly load the update - i look under networking and nothing seems to be happening.

Thanks for all the continued help, must go my girlfriend is hassling me for being too long on the computer and staying up too late,
James

 

[c0rv1d43]

Well, the modem's vendor may eventually come up with an appropriate driver. If you grow tired of waiting, however, one of the U. S. Robotics modems will get you connected at the best speed possible for your line. I've had wonderful luck when helping other people with them. (Alas, I've never owned one myself!) If you decide to try one read up on the models that are available. Some have some special features that might, or might not, be useful to you. There's no reason to spend extra money on features that won't be used.

Best of luck to you, James. It's been a pleasure.

Regards,
Collin

 

[JamesC]

Hi again Collin,
I have been trying to get that Sdelete program that you recommended me to use to work. DOS really is not my strongpoint. once i have it on the floppy what command should I use. I tried: run sdelete.exe

Also would it have to actually be on the boot disk or could i boot up with the boot disk and then swop disks and run it?
thanks for the help,
James

 

[c0rv1d43]

Hi, James.

I hesitate to tell you exactly what command to issue. You should save the Web page from which you downloaded the sdelete utility and read the directions carefully to be sure you understand all of the ramifications. Of course if you're wiping the drive anyway I guess it won't hurt to experiment.

The sdelete utility is small and will fit on a standard WinME or Win9X boot diskette. You run it at the command line, NOT from within Windows. So you don't use "run". For instanc if you just boot to the A:\> prompt with the diskette in the diskette drive (Make sure you boot to true DOS by booting with the diskette in the drive and with the BIOS set to boot first from the floppy drive.) and issue this command

sdelete -p7 -s c:\*.*

then sdelete will overwrite every file and subdirectory on drive c: seven times.

I hope this helps.

Regards,
Collin

PS: You might just want to format drive c: first then issue the command

sdelete -p 7 -z c:

The "z" switch just tells sdelete to overwrite or clear all "free" space on the drive. (Once you've formatted the drive, then all of the space on it is free space.)

 

[JamesC]

Hi Collin
I tried what you said but all i got was the message - this program does not run in DOS.
Obviously that is not the case but i cant seem to get it to run. I tested it by running in the msdos prompt through windows and the black page flashes up very briefly and then dissapears although it does have writing on it. Any thoughts on what is going on. i booted into dos using the startup disk, then i put the command you said in but no success.
thanks, james
ps i also fiddled a lot with the commands trying everything i could think of.

 

[c0rv1d43]

I tried what you said but all i got was the message - this program does not run in DOS.
Obviously that is not the case but i cant seem to get it to run. I tested it by running in the msdos prompt through windows and the black page flashes up very briefly and then dissapears although it does have writing on it. Any thoughts on what is going on. i booted into dos using the startup disk, then i put the command you said in but no success.
thanks, james
ps i also fiddled a lot with the commands trying everything i could think of.

I'm wondering if I've misled you with respect to the way the program works from the command line. Let's try this from the beginning.

1. I think I may have been wrong to tell you to boot to DOS with a diskette to run the program. I was assuming that this would work since sdelete is a command line interface utility. (I don't use DOS. Don't have it installed on anything.)

2. It's possible the program has to be run from within a DOS command line window from within Windows. If that's so, then the utility isn't going to do you a lot of good for wiping the whole drive, though it can at least wipe out files and directory structures to which you direct it, and it can also wipe the hard drive's free space.

3. You said that you put in the command from DOS "but no success". What exactly happened?

4. If you open a DOS command line by going Start | Run, typing in the word "command" (no quotes) and hitting the Enter key, then if you type the sdelete command at THAT command prompt, what happens?

- Collin

 

[JamesC]

Hi Collin
One slight problem with trying to run the program from inside windows, i have allready wiped it off! All i can do at the moment is boot from the startup disk, untill i reinstall windows. I will try to run it again to let you know what the message is exactly and i will post again in about ten minutes - it takes me a bit of time as i only have 1 keyboard and have to swop them over.
James

 

[JamesC]

the exact response is:
This program cannot be run in DOS mode

and here is what i have tried:

sdelete -p 7 -z c:
sdelete
sdelete -p7 -zc:
sdelete [-p 7] -z [c:]

James

 

[DualXP4ghz]

At the login screen just hit ctrl + alt + delete 2 times and the type in administrator and your password if you have one. I dont know if that already in here in this post, but I didnt want to read the entire thing. But that works for me

 

[c0rv1d43]

Originally posted by: DualXP4ghz
At the login screen just hit ctrl + alt + delete 2 times and the type in administrator and your password if you have one. I dont know if that already in here in this post, but I didnt want to read the entire thing. But that works for me

Heh-heh. If you don't want to read the whole thread then it's probably best not to try to answer. We're already a LONG way past that issue.

- Collin