hi gang,
I'm trying to troubleshoot this issue I'm having with the we-diag ap. I
keep getting an error that tells me it's an overflow on line 501. Well
upon opening the script in notepad, it's all gibberish. So I did a test
of the same ap on my other computer and it ran perfectly fine. On the
computer with the problem ap, I have uninstalled and reinstalled it,
deleting the .ini as well but that hasn't helped.
I'm wondering something that just occured to me as I was writing this. I
have a ramdisk installed, if the we-diag is querrying that for info,
it's only 500 mb for some small files I use quite frequently, could that
be the overflow issue? I'm not really enclined to stop the ramdisk from
running as I had a hell of a time trying to get it running in the first
place. If the ramdisk isn't the problem, then what does overflow
constitute in this context? I have a quadcore and 16gb of ram, so memory
isn't the issue, at least that's my presumtion.
I'm wondering, as per the subject line, if there is soemthing I've
missed when removing the ap via the add/remove aps interface, and thence
removing the .ini file?
so any ideas on this are welcome, I'm open to suggestions. Knowing me,
it's probably soemthing that's really easily fixed and I'm making a
bigger deal out of it than necessary.
--
Dave C. Bahr
Facebook: Dave Bahr
Twitter: dcbahr
If you reply to this message it will be delivered to the original sender only.
If your reply would benefit others on the list and your message is related to
GW Micro, then please consider sending your message to [email protected] so
the entire list will receive it.
GW-Info messages are archived at http://www.gwmicro.com/gwinfo. You can manage
your list subscription at http://www.gwmicro.com/listserv.
