Question:
NEVERMIND UNLESS YOU REALLY WANT TO ANSWER THIS :does puppy come with web,ftp,php,perl,mysql,sendmail?, Or better yet how hard would it be to set all that up using puppy(or suggestion for proper distro).
Problem:
Downloaded puppy2.12 did the md5 check passed burned to cd using nero, but with ANY of my p4 and amd machines I get boot error
error: Disk error 32, AX = 4200, drive 9f
Please help want to try this distro.
Burning questions, problems
burn slow
Hi, and welcome. Just burn it slow: 2X or 4X.
As to your other question, search for "business" here in forum.
As to your other question, search for "business" here in forum.
Puppy user since Oct 2004. Want FreeOffice? [url=http://puppylinux.info/topic/freeoffice-2012-sfs]Get the sfs (English only)[/url].
Please re-consider - an md5sum pass - just ensures the download was good - NOT that the burn was !
Choosing a "slower" feed > Good burn utilitities always employ whatever the device supports !
It MAY help -(can't hurt) but seldom root cause :
A good burn utility/methods > should monitor progress - use "buffering" of data feed before
passing data to write utility.
Suspect media - or even just a scratch or smudge I.E in lead-in tracks containing read data - may disrupt whole boot process.
When "coaster" was confirmed as bad -& consistent error MSG -relating to own drives
and not confirmed of SAME Problem as reported when used by others _
First suspect - burn methods. options used :
TAO/DAO etal.
Re-write media - was it closed session or :
Was "fixated" used ?
MANY possibilities - no burn utility result summary ?
PROPER system ?? = use what is supplied - - then re-master contents to own taste !.
Good luck & hang in there = the results (Puppy) are worth it !
Choosing a "slower" feed > Good burn utilitities always employ whatever the device supports !
It MAY help -(can't hurt) but seldom root cause :
A good burn utility/methods > should monitor progress - use "buffering" of data feed before
passing data to write utility.
Suspect media - or even just a scratch or smudge I.E in lead-in tracks containing read data - may disrupt whole boot process.
When "coaster" was confirmed as bad -& consistent error MSG -relating to own drives
and not confirmed of SAME Problem as reported when used by others _
First suspect - burn methods. options used :
TAO/DAO etal.
Re-write media - was it closed session or :
Was "fixated" used ?
MANY possibilities - no burn utility result summary ?
PROPER system ?? = use what is supplied - - then re-master contents to own taste !.
Good luck & hang in there = the results (Puppy) are worth it !