utTraceStar: analyse your iBurst connection

Seburn, the Saint

Just to thank Seburn for spending over 2 hours in the middle of the night to help me get utTraceStar running with the new black UTD.:D

Thought I saw Sanlam building, but now I know I'm looking at Linksfield bouncing from the neighbours house and then off my back wall!

Thanks again!!!
 
Hi,

I'm having trouble using your application.

I've got a reletively new iburst modem which is orange in colour but looks just like the new black ones.

I've manually set the IP of my ethernet point to 192.168.250.1 and subnet to 255.255.255.0

I'm not using any of the iburst software to connect, I connect via a crossover cable straight to the modem and use XP PPPoE to dial the modem.

When I start up the application it fails to pick up the IP and wants the wizard to run. If I choose to not use the wizard, then I'm presented with the application with no details on it.

If I follow the wizard and choose ethernet I get the following.

See the end of this message for details on invoking
just-in-time (JIT) debugging instead of this dialog box.

************** Exception Text **************
System.Management.ManagementException: COM object that has been separated from its underlying RCW can not be used. ---> System.Runtime.InteropServices.InvalidComObjectException: COM object that has been separated from its underlying RCW can not be used.
at System.Management.IEnumWbemClassObject.Clone_(IEnumWbemClassObject& ppEnum)
at System.Management.ManagementObjectCollection.GetEnumerator()
--- End of inner exception stack trace ---
at System.Management.ManagementException.ThrowWithExtendedInfo(Exception e)
at System.Management.ManagementObjectCollection.GetEnumerator()
at g.c(Object A_0, EventArgs A_1)
at System.Windows.Forms.Form.OnLoad(EventArgs e)
at System.Windows.Forms.Form.OnCreateControl()
at System.Windows.Forms.Control.CreateControl(Boolean fIgnoreVisible)
at System.Windows.Forms.Control.CreateControl()
at System.Windows.Forms.Control.WmShowWindow(Message& m)
at System.Windows.Forms.Control.WndProc(Message& m)
at System.Windows.Forms.ScrollableControl.WndProc(Message& m)
at System.Windows.Forms.ContainerControl.WndProc(Message& m)
at System.Windows.Forms.Form.WmShowWindow(Message& m)
at System.Windows.Forms.Form.WndProc(Message& m)
at System.Windows.Forms.ControlNativeWindow.OnMessage(Message& m)
at System.Windows.Forms.ControlNativeWindow.WndProc(Message& m)
at System.Windows.Forms.NativeWindow.Callback(IntPtr hWnd, Int32 msg, IntPtr wparam, IntPtr lparam)


************** Loaded Assemblies **************
mscorlib
Assembly Version: 1.0.5000.0
Win32 Version: 1.1.4322.573
CodeBase: file:///c:/windows/microsoft.net/framework/v1.1.4322/mscorlib.dll
----------------------------------------
utTraceStar
Assembly Version: 1.0.13.29852
Win32 Version: 1.0.13.29852
CodeBase: file:///C:/Documents%20and%20Settings/Robin/Desktop/utTraceStar/utTraceStar.exe
----------------------------------------
System.Windows.Forms
Assembly Version: 1.0.5000.0
Win32 Version: 1.1.4322.573
CodeBase: file:///c:/windows/assembly/gac/system.windows.forms/1.0.5000.0__b77a5c561934e089/system.windows.forms.dll
----------------------------------------
System
Assembly Version: 1.0.5000.0
Win32 Version: 1.1.4322.573
CodeBase: file:///c:/windows/assembly/gac/system/1.0.5000.0__b77a5c561934e089/system.dll
----------------------------------------
System.Drawing
Assembly Version: 1.0.5000.0
Win32 Version: 1.1.4322.573
CodeBase: file:///c:/windows/assembly/gac/system.drawing/1.0.5000.0__b03f5f7f11d50a3a/system.drawing.dll
----------------------------------------
System.Management
Assembly Version: 1.0.5000.0
Win32 Version: 1.1.4322.573
CodeBase: file:///c:/windows/assembly/gac/system.management/1.0.5000.0__b03f5f7f11d50a3a/system.management.dll
----------------------------------------

************** JIT Debugging **************
To enable just in time (JIT) debugging, the config file for this
application or machine (machine.config) must have the
jitDebugging value set in the system.windows.forms section.
The application must also be compiled with debugging
enabled.

For example:

<configuration>
<system.windows.forms jitDebugging="true" />
</configuration>

When JIT debugging is enabled, any unhandled exception
will be sent to the JIT debugger registered on the machine
rather than being handled by this dialog.

If after this point I try to continue I get a screen saying that I must report "error 506:specified argument out of range of valid values.Parameter name:index" to the developer
 
Those errors are related to the wizard. Don't click yes to use the wizard it seems to be quite commonly people get that error.

I cannot reproduce it. Just set the IP manually.

Either disable your firewall or add a rule for 192.168.250.x and utTraceStar. (windows firewall included). If you cannot open telnet (start run telnet 192.168.250.10 1234) then the problem is with your computer (firewall etc) or In a few cases the modem.
 
Well it took a format and reinstall to get utTrceStar working, but its working :)
 
Hectic! I wonder if some windows update is causing trouble? Did you do windows updates?
 
Interesting, I'm using the USB modem but I've managed to get the software working via the wizard selecting the ethernet modem.
 
utTraceStar "Connecting"

Hi Seburn. This is a great program for setting an external directional antenna.

When using it, I have to disable my firewall. It took me a while to discover this.

Sometimes, it goes through the setup routine despite having been used successfully before. Resetting the modem (USB implementation) always solves this problem.

When running, it reports connection to BSs other than 27 at which my antenna is aimed. Are these spurious connections? (pcVtalk does not show these connections while running).

It would be very considerate of iBurst to show the BS number on their Network Status. It appears that there are duplications caused by reusing numbers on new BSs. This would be of great value in redirecting antennas in the event of one's chosen BS going down.
 
Thank you for your feedback I will be looking into these issues in the .net 2 version of the application. Which will be released next year sometime.
 
When trying to run utT, I get an error message that the Beta version has expired. Have checked on website - I have latest version 13. What do I need to do?
 
I'm getting the same error...Beta version has expired.

Resolution?
 
Hi there,

Sorry about the expiratation of the beta version.

The expiration is meant to help people stay up to date with various improvements in the product.

(I have many big plans for utTracsStar still in the pipe lines)

Unfortunatly due to the amount of work load I have had recently I have been unable to make these planned advancements.

Now I have to release 1.0.14 which has just had the date changed. Which I agree is a royal pain in the ass!

Sorry for the inconvience this has caused I do plan on more improvements and set the date to 2008 just in case.

However I cannot access the ftp therefore cannot upload the release so. Unfortunately we ganna have to wait till that gets fixed. Look out for 1.0.14 comming soon.
 
Hi Seburn

Thought I would let you know about this little bug, if you can call it that. But a few months ago I posted a issue on this thread , where the app would launch but not actually display any data in the data fields or anything in the graph. It never was resolved so I went on my merry way.

At some point in time I removed a bunch of crap off my pc and guess what it worked again, seeing that I never noted everything I removed I could not explain what it was. A few weeks passed and I needed to load a codec for a .mov file. I loaded the codec and utTraceStar broken again , unloaded and it worked.

Really weird I know, but thought I might share this info with you , might be worth something, might just be my dodgy pc.
 
Ftp problems still causing trouble.

Ontop of that somehow the source files were corrupted... is the only way I can explain it.

I will have to revert to ver 1.0.9 but will make whatever adjustments I can.

I was hoping to move over to .net version 2 now seems like a good time to do so.

Will keep u posted
 
Hi
Since the beginning of the year when trying to run UTTraceStar, I get the following message: " BETA Expired!! To Ensure that you are up to date with your version each beta release has an expiry date", I downloaded the latest version, deleted the old files and I'm using the new ones, however I still get this message. Any ideas on how to resolve this?
Thanks
Theo
 
theogroenewald said:
Hi
Since the beginning of the year when trying to run UTTraceStar, I get the following message: " BETA Expired!! To Ensure that you are up to date with your version each beta release has an expiry date", I downloaded the latest version, deleted the old files and I'm using the new ones, however I still get this message. Any ideas on how to resolve this?
Thanks
Theo
Click to expand...
Workaround only at this point :- Change your system dater back a year and relaunch. :)
 
You must log in or register to reply here.
Back
Top
Sign up to the MyBroadband newsletter
X