BurningShadow has released LiveCD4, which is based on LiveCD3, but uses a RAM disk, which makes it more stable and easier to use. Unlike its predecessor, this CD doesn’t require floppies or other writable storage to boot. The CD image is available for download here. An installation CD, InstCD1, is also available, with which you can get a system similar to that on LiveCD4 installed permanently.
Download – Burn – Boot: Syllable LiveCD4
About The Author
Eugenia Loli
Ex-programmer, ex-editor in chief at OSNews.com, now a visual artist/filmmaker.
Follow me on Twitter @EugeniaLoli
Syllable is fast, but still not very stable yet (which is to be expected since it’s not mature yet). Looks very promising, though.
Syllable looks promising – in my opinion the most promising of the hobby OSs. If nothing else, they keep making more and more releases to the public.
I cant boot it in vmware. It pauses in the ramdisk initialization. Anyone else tried in it?
Check here
http://syllable.sourceforge.net/faq.php?cat_id=3&cat_name=Vmware#6
With an emulator, you don’t have to repartition your HD, in order to create a new partition, so I think you should install the real thing. You could use <a href=”http://syllable.burningshadow.dk/news.display.php?id=12“>InstCD1… to get a system, that looks like the LiveCD. And then it’s a lot better
Tell me if that works
Good job BurningShadow! I’m been following your progress on the mailling list.
I’m = I’ve 😉
But what architectur is Syllable written for?
I don’t want to download a huge iso, just to find out it’s not x86.
its x86
I tried it on 2 PCs and and it didn’t boot – init error.
Does it say something about, not finding the boot device?
What is your hard ware configuration (chipset/cd drive etc.)
Thanks. =)
I’ll give it a try once I’ve freed up some hd space for the iso file.
Syllable has never booted on at least four of my machines, all with different hardware. I would like to send the hardware configurations and crash information back to the developers. Is there a tool to create the info or a list of information that they would like me to send somewhere?
Yes, try the Syllable forum:
http://syllable.sourceforge.net/forum.php
or the mailing list:
http://lists.sourceforge.net/lists/listinfo/syllable-developer
downloaded the install iso, up and running!
A summary of what Syllable LiveCD4 is would have been nice.
I really like what syllable is and how its shaping up. I used to follow the progress of AtheOS, and am happy to see that its offshoot is doing so well.
Once syllable gains more applications, it’ll be a nice OS to run on my work laptop.
Keep up the good work…especially you BurningShadow, I wouldn’t have tried this without the existence of a livecd.
Syllable has never booted on at least four of my machines, all with different hardware.
Have you tried LiveCD 3 or LiveCD 4? We’ve re-written the ATAPI layer to work with more CD and DVD ROM drives. The new driver is not in Syllable 0.5.3 but is included in LiveCD 3 and 4, and will be released with Syllable 0.5.4. You could give them a try and see if Syllable will now boot on your machines.
I would like to send the hardware configurations and crash information back to the developers. Is there a tool to create the info or a list of information that they would like me to send somewhere?
There is a kernel debugger via. the serial port which can be used to capture the output from Syllable as it boots, or you can just write down the messages you see on the screen. If you have tried LiveCD 4 and it fails, you should include full details of the machines hardware and the messages the kernel printed when it tried to boot. You can either send a message to the Syllable-Developer mailing list or post the details on the syllable.org forums.
Have you tried LiveCD 3 or LiveCD 4? We’ve re-written the ATAPI layer to work with more CD and DVD ROM drives.
Still doesn’t work on my two machines
atapi error, unable to load fs driver etc.
They have widely used Lite-on and NEC drives in them. All standard hardware.
Would a boot floppy solve the problem?
Is there any chance you could write down all of those ATAPI errors for me? There the useful information I’ll need to be able to debug the problem. Can you also tell me what motherboard chipset you have and how your hard drive(s) and CD-ROM drive(s) are configured?
They have widely used Lite-on and NEC drives in them. All standard hardware.
Lite-on…oh goodie. Not to put too fine a point on it, some hardware is far more standard than others. I’ve heard that even Linux has problems with some Lite-on drives..
LiveCD3 and LiveCD4 have never booted on my homebuilt Soyo PXP400 Dragon Lite with 2.6Ghz Celeron, Exact DVD(also tried Verbatim CDRW), 8X AGP with one/two hdds.
The boot always stops at
:Decoding partition table hda
It booted fine though on my old Dell PIII i810 Mobo. What little I saw of Syllable there I really liked. Keep up the good work.
Booted into LiveCD twice now. Used Root/Root as user/password. Odd thing, each time I booted the desktop was different.
The first time the desktop was dark blue with large “Syllable” logo in center. Clicked “Home” folder which opened up and displayed several more folders including “Applications.” Then, nothing. Clicking on the icons made them flash, but nothing ever opened again.
The second time, the desktop was a blue-gray color with small Syllable log in lower left corner. Clicking on folders did nothing but ‘blink’ the folders. The Console did open and executed the “Dir” command just fine. But then it was tricky to close the console – the button was off the top of my monitor. And then all of the desktop folder icons disappeared completely.
Don’t think it’s ready for use yet. But at least it booted…
-Bob
Previous post should have been “Terminal” rather than “Console.”
Third boot was very interesting. Was able to open one of the folders and change the desktop settings. After increasing the resolution, a menu bar appeared at the top of the screen. Background went black though, and entire OS was frozen…
-Bob
Thats interesting behavour; it sounds like reading from the CD-ROM fails occasionally so things like libraries or configuration files are not loaded correctly or are loaded but corrupt. It could be a bad CD, a broken CD-ROM drive with intermitent read-failures, or more likely, a bug in the ATAPI code. The only way I can tell for sure is to see a full kernel log from your computer, but there is no easy way to get it from the LiveCD unless you have a null modem cable and a second machine.