Release Candidates :: DSL-2.0RC1



DSL-2.0RC1 Tested on my much older..
Toshiba 400CDT Satellite Pro Laptop
Intel P75 Mhz Cpu
24mb Ram
777mb HardDisk

Chips & Tech. Accelerator <-- works in 640x480 Res
Chips_Technologies 4.0 Graphics
I havent gotten DSL to work in other resolutions only the 640x480 Res on this machine but it works good, (although old) this is a color screen laptop and the DSL desktop looks great on here.

With a 28.8 Motorola @World ext hardware dial up modem
and Toshiba CD-Rom XM-1202B / CD Drive.

The 28.8 Motorola @World ext hardware modem works great in DSL, see's it right away and gets to work dialing out after the config.

The Toshiba CD-Rom XM-1202B / CD Drive <-- doesnt work with DSL and was always known to be a pain as it even required its "own" Toshiba supplied driver to use it in DOS so no surpise it isnt seen by DSL.. The modem and surfing the web in Dillo works great, FireFox is bit hardware intensive and so its slow, but Opera works quite well and at a tolerable speed. (meaning less swapping)

DSL-2.0RC1 works just as good on here as 1.2 thru 1.5 did. :)
In fact maybe its just me but 2.0RC1 seems a little faster.. (the kernel update maybe?) :)

Thanks for supporting older but still useful hardware. :;):
Just wondering im a beginner in linux, just wondering
if you could point me in the right direction for help & actual operating system, i've got a USB KEY, im actually interested in Damn Small Linux for me to try to learn on.

Thanks
Just wondering does it support on 64 bit hardware???
It doesn't directly support 64 bit architecture. You can get started by reading the wiki and the FAQ. You can make a USB key that will boot from SOME computers that support booting from the USB key drive. Many older ones don't. Almost all computers support booting from the CDROM drive, if they have one, but you often need to set it up in the computer's BIOS.
I know that SaidinUnleashed mentioned at the start of the thread the big things that need testing for this RC.  Can somebody put out a set of basic instructions of how to test the thiing that have changed.  I'm not looking for anything like formal test scripts, but a little direction would be nice.

I have access to an array of old and new hardware between work and home, but I'm not sure how to test, other than poking around randomly until something doesn't work (nothing so far!).  I feel like this is inefficient, since I'm probably not using some things that are importatnt to a significant portion of the users.  I'd like to make the best use of the time and hardware I have available for DSL, especially as I am quickly moving towards using it as my main desktop OS.
Next Page...
original here.