I am Mark Weiss. I did have a ton of issues.
I am not smart enough, alas, to grind through it all to find out
every reason why.
I was stable with OS9 and Tango T1,T2,T3,T4, ok basically all the
versions, until we loaded it up. Been using Tango/Witango since
Butler and Beta software. Runs three of our businesses.
I thought MacOSX and Witango 5.5 would be more stable and robust. So
we tested for a while and switched.
Under load things fell apart constantly.
About a six months ago, I began talking with Robert and we both tried
and tried to stabilize things.
Nothing lasted. I finally said uncle and suggested the unthinkable.
MY ISSUES
I have found taf's that for whatever reason, have issues that I
believe brought thing down or destabilized things. So my bad on them.
I take responsibility for that.
WITANGO ISSUES
Witango was unresponsive to about a 1/2 a dozen requests on the
server. Just no answer. or no answer that was an answer. Sorry, I
love those guys and know they are doing their best, but no answer
doesn't cut it in a business environment. Sorry, but true. It
probably is that I am a pain, because I just know enough to get
myself in trouble.
Witango was/is unresponsive to issues with OSX Dev Studio. We have
verified that for some reason, with our db Primebase, either Witango,
or the OpenLink ODBC Driver, somehow the dev studio takes a perfectly
good taf and rewrites the definition of a field to !CST instead of
vcha, or date or tims or..... When this happens all kinds of things
break. Notably, the time, date and timestamp fields.
After editing in Dev Studio, I load the taf into BBEdit and exorcise
all of this code and clean it up. The taf's at least, after that work
right.
I have no idea why this happens. Witango has responded I believe once
to this problem, asking questions. By the time they did, I made a
business decision....
Robert had Windows servers serving tons of stuff, under heavy load,
and not cracking, or at least not that he admitted to me. Our needs
are very very modest in comparison to his. If he can make something
stand up to a large load, and work day in and day out, then at some
point I have to run my business. Man this is hard to admit. As hard
as it was to abandon my All Mac Dream in our office, on the server
side I finally decided to put in a Windows Server, and a very nice
machine, to the specs Robert suggested. He has done most of the work.
This has been running now for 1 week. 90% of the problems we had have
disappeared. I have cleaned up a few .tafs that had some kind of
corruption in the Joins. It is even more stable now than 1 week ago.
All our desktops are mac and I wouldn't change that for one minute
and neither would any of our employees. New hires come begging for a
mac within about a month of being here. But OSX Server and Witango
are not dancing together and suspect won't for quite some time.
Again, probably a business decision. Not trying to speak for Witango
in any way. But that is my gut feeling.
The office staff and outlying warehouses who connect, are beside
themselves with the speed and with the stability.
Again, this is very hard for me to say, as a mac guy, but it appears
to be a sound and good business decision on the server side.
I might also add, that I have always found the mac community to be
very helpful to wannabes like me... Until OSX. When I tried to get
help on the Apache List, and OSX Server List the Unix Geeks were for
the most part unhelpful and impatient with the likes of a code
cobbler like myself. Perhaps that will be the same on the Windows
side. But I hope not.
I still use the Mac Dev Studio. And now having used both, Command-
anykey on the Mac works so much better than
control-somekeyorFkeyorsomethingelseIcannotfigureout that takes two
hands to do on a windows box. Again, like someone said to me
recently, Dev Studio has to be dumbed down for the Mac guys ;-).
So there you have it. Confessions of a "died in the wool mac guy".
Hell has frozen over. I hope no one takes this wrong or gets
offended. However, if you do, and want to flame, flame away. I have a
really thick skin. I hope that someday the mac side at Witango can
prove to me it is just as stable and a valid business decision. We
will see. For now it isn't. And I don't have the time to make it so.
Others may or may have to, but we don't.
Yours,
Mark
On Oct 3, 2005, at 7:06 PM, Robert Garcia wrote:
Mark Weiss was having a ton of issues, over and over. Ask him about
what seems to be working for him.
--
Robert Garcia
President - BigHead Technology
VP Application Development - eventpix.com
13653 West Park Dr
Magalia, Ca 95954
ph: 530.645.4040 x222 fax: 530.645.4040
[EMAIL PROTECTED] - [EMAIL PROTECTED]
http://bighead.net/ - http://eventpix.com/
On Oct 3, 2005, at 6:26 PM, Wayne Irvine wrote:
Here's a crash log entry covering one crash.
I've looked through it and the pertinent bit seems to be the last
line:
Link (dyld) error:
dyld: /Applications/WitangoServer/5.5/./witangod can't open library:
libjs32.dylib (No such file or directory, errno = 2)
Anyone know what this is?
Wayne Irvine
Byte Services Pty Ltd
http://www.byteserve.com.au/
[EMAIL PROTECTED]
Ph 02 9960 6099 Mob 0409 960 609 Fax 02 9960 6088
_____________________________________________________________________
___
TO UNSUBSCRIBE: Go to http://www.witango.com/developer/maillist.taf
<crashlog.txt>
______________________________________________________________________
__
TO UNSUBSCRIBE: Go to http://www.witango.com/developer/maillist.taf
________________________________________________________________________
TO UNSUBSCRIBE: Go to http://www.witango.com/developer/maillist.taf
