From their press release: “Now, yellowTAB presents a fully-functional, fully-featured implementation of ODBC (Open DataBase Connectivity) for Zeta! Both the API and the user interface for configuring ODBC connections is 100% compatible with the original Windows version and its UNIX clones.”
Both this and the fact that yT is beginning to keep the visitors to its site more in the loop are welcome news.
yT doesn’t envision Zeta becoming a server platform but I actually see it becoming just that. I think there’s room to be an easy-to-admin server system (easier than linux and cheaper/more stable than windows).
Anybody else with thoughts on this and ODBC?
I read some days ago on http://www.yellowtab.com/article.php?id=46
that they want to port MLDonkey.
I think this is much more important than ODBC connectivity, since BeOS has always been targeted at home users not business people.
Therefore I wonder, why the MLDonkey port was not announced here but the ODBC connectivity…
Therefore I wonder, why the MLDonkey port was not announced here but the ODBC connectivity…
Slow news day . . . editors preference . . . it’s not black magic, you know. Besides, supporting ODBC only required a recompilation of the *nix code, its not as if yT spent months working on this. The MLDonkey port is just another app ported, no need to report this on OSNews.
Either way, waiting for Zeta (Deluxe Edition).
Hi Max.
we said not we “want” we said we DID it
You have both now, ODBC AND mlDonkey in Zeta
Will it “just work” or can we expect all the hazzle from Zeta as we have with R5 now?
Have you done something about the issues that really matters? Or is that why it’s referred to as vapourware?
Vapourware is your mind!
What does ACPI have to do with anything re BeOS problems?
Has yT done something about the 1 Gig memory limit?
Adam
Because if you buy a computer today it will use ACPI most likely, and BeOS don’t like that. Shared IRQs makes it go crazy, and for mr joe user, modifying things in Bios and switching physical slots for HW not their thingie.
BeOS can’t handle plug n play AT ALL, so some serious kernel hacking has to be done, and so far we haven’t read much about any kernelhacking at all as far as I know, exception USB stack.
Does it matter how good an OS is if you can’t install it and boot it?
Hi Bernd,
wow that’s even better Just for curiosity: Did you “only” port the engine or also some GUI for it?
And as I already have the honor to talk to the creator of a new BeOS, what network connectivity will you offer when the product is released? Since I am in a VPN network and need (unter linux) the pptp-client to connect to internet, I want to know if it (theoretically) possible to connect to the internet over an VPN connection with this pptp-client (also needed for some Austrian and Spanish ADSL providers AFAIK)?
Because I think, that in todays world, an OS without Internet is useless.
However, good luck with Zeta, and keep going – hopefully it will even surpass all of our deepest imaginations
—-
BTW: Grüße aus Österreich
I connecting by Satalite from tiscali to Internet and this direct from Zeta. And Zeta have a far more better xDSL support then BeOS.
Grüsse aus dem Norden Hamburgs
I am getting increasingly impressed. With the announcements, at least. But if I added my url to this message, it would get moderated down…
Good job, Yellowtab. Put me down for the Developer Edition as soon as it is available.
IIRC, there is already a free available implementation by Intel which is going to be used in Linux, and IIRC, it is licensed under the BSD license.
As in the acpica lib that FreeBSD 5.x is using?
“there’s room to be an easy-to-admin server system (easier than linux and cheaper/more stable than windows). ”
Say : Novell, Mac OS X Server ?
—
http://homepage.mac.com/softkid/PhotoAlbum4.html
Hey, what are you doing posting here? Aren’t you supposed to be working on the next Gortican album?
Your comments on BeOS’s handelling of Plug and Play are utter crap. BeOS has had the only real implication of true Plug and Play I have seen in any OS and OS/X and Windows can’t even live up to what Be Inc. had achieved.
Your comments are full of it. Sorry but true. Try changing your computer CPU along with Motherboard, Video card, Sound card and memory type with both Windows and BeOS (keeping to supported hardware for both platforms). You will find the only OS to work out of the two with absolutely no preparation or settings changes will be BeOS. You will boot into the exact same desktop resolution and colour depth with all other user settings in place and you are ready to just use the machine.
Windows will fail to boot and will require a re-install.
If you use hardware with drivers that are not yet on your BeOS system just install drivers required for hardware before changing hardware components and bingo a painless transition.
Next?
Piers :
While I agree that XBe is way off the mark (BeOS definitely has the best “true” plug’n’play of any desktop OS to date), Windows is not as bad as you make out.
Win2k will throw up a bunch of hardware-installation dialogues when you swap boxes, and might trash a few of your old drivers, but it _will_ boot. XP (Corporate) is even better in this regard (I won’t get into the reactivation requirements of the consumer XP…).
Its not at the comfortable “one drive boots anywhere” level that I have with BeOS, but it works when it has to.
Anonymous, your post is absolutely correct. The BeOS “it’ll boot just as before” capability is better, sure, but every time I’ve done that with Win2k/XP, it’s worked just fine, too. Yes, it will put up a minute or two of “installing new ______” dialogs, but it’s certainly acceptable. Hell, how often do you do it? Moving the hardware takes well more than the minute it takes for Windows to reconfigure things.
I’m certainly happy giving the BeOS credit where credit is due (and yes, it’s very good about finding hardware), but you don’t have to spread false information about Windows in the process.
I’m sure XBe meant the PNP standard, not the connotation of the phrase
Correct!
ACPI comps and BeOS doesn’t work well together that’s just the way it is. Try buying a new comp today (like a P4 2.0ghz or higher) which is ACPI enabled and also have quite a lot of HW that shares IRQ’s and we’ll see how lovely BeOS will just boot on that *irony*.
I love BeOS more than any OS, but I wanna see it evolve and I haven’t seen Zeta address any of these important issues which will be crucial for people who might just wanna try the OS. Zeta is like BeOS Max but costs money.
and you know that…
OpenGL, BSD Stack, new APIs, new interessting apps
blah blah
Why just people post things that aren’t right…
Regards
-A
Well, I had BeOS running on a 2 Gig P4, with an adaptec SCSI Card, Brooktree TV capture card, an Intel NIC, a Realtek NIC, an on board C-Media audio chip (impossible to disable in the BIOS), a SB Live!, and a Radeon 8500…
Funny, but BeOS had no issues with this configuration…
On the contrary, I’ve had a motherboard die on me on a windows box. I replaced with a completely different motherboard (went from a Tyan/VIA motherboard to a FIC/Intel motherborad), and Windows XP completely failed to reboot. I had to “repair” the installation to get it going again.
Oh, and then I had to call that stupid 1-800 number because MS apparently thought I was a thief.
Adam
XBe,
ACPI is a power management standard, not IRQ management.
Windows assigns IRQ’s to PNP compatible devices, BeOS does not. BeOS reads what IRQ’s the BIOS assigns, since the BIOS is lower level it should have a better handle on what hardware is present thus be able to assign IRQ’s more efficiently.
By default, most BIOS’s let the Operating System assign the IRQ’s because most computers run Windows–and Windows will assign the IRQ’s even if the BIOS had already assigned them (which can cause other problems). So, in reality, by “disabling PNP in the BIOS” you are actually enabling the BIOS to do the PNP configuration instead of the OS.
Now, do you know what an IRQ is? DMA? Memory Address? If you want to learn how your computer works, I’ll be more than happy to help you out.
landar_c