The Other Board (Hobart)

[AV8OR]

What's going on with the Hobart board? I keep getting redirected over to the blue side. Anyone else having problems?

[ASKANDY]

I haven't heard anything unless it's down for maint???

Seems to be working for me.

A-

[fatfrank]

Yeah, I get directed here also?????

[migmaniac70]

was having same problem, so i deleted the links out of my favorites and did a search on hobart, then had to drag and drop them back into my favorites and now everything is fine.

[ASKANDY]

That's strange!!??
a

[Scott V]

was having same problem, so i deleted the links out of my favorites and did a search on hobart, then had to drag and drop them back into my favorites and now everything is fine.

Send a link ?

Thanks

[migmaniac70]

Who knows? maybe it was only happening to AOL users. before it was redirecting me to the Miller site but now it's working fine.since i re-did it all.

[fun4now]

no go for me

i'm a AT&T .com'er not AOL and i get the same redirect ARRRRG bit of a pain i hope they fix it

[migmaniac70]

http://hobartwelders.com/ try this, i know it's the same but it worked for me. http://hobartwelders.com/mboard/

[AV8OR]

No AOL here either, AT&T. I had to do like you said by deleting the old link and add a new favorite link.

Sometimes I think I might go back to using smoke signals again!

[migmaniac70]

gotta love technology

[fun4now]

seems to be working ok again for me i didnt do anythig it just started working again
hummm they must have herd about the smoke signals ideal and decided they fix it befor we all switch back

[migmaniac70]

Whats really messed up is once i fixed the Hobart board, i clicked over to the miller board and got some crap about it being the default homepage for PLASK!! it finally streightend out though

[fun4now]

net crash

sounds like the net is crashing
gess we beter get the fires started, lets see maybee i can use some old shop rags for the smoke signals

[INTP]

I had the same problem last year. If I recall, I upgraded to a new browser version (mozilla) and it fixed it. At the time, I was getting the problem in Mozilla, but not IE. I never figured out why it just started happening.