Installed Slacko 5.7.0.
First, when streaming video,the screen sometimes goes dark but the audio remains. And sometimes the mouse disappears at the same time.This did not occur in slacko 5.6.
Second, I am able to boot the 5.6 iso using grub4dos;but with the 5.7, it fails totally. I looked at the 5.7 iso using poweriso, and it showed the iso to be bootable.(Iforgot to look for 'loopback cfg')
What gives?
Streaming video goes dark in slacko 5.7.0
Looks to me like a bad install and or download of Slacko 5.7.
If Slacko 5.6 worked OK. Slacko 5.7 should be the same or better.
Some specific details on what you did would help.
Downloaded iso from where?
Installed how?
To what?
Graphics setup you are using?
Some computer details.
What is it?
Any Slacko 5.6 files on the installed to device?
If Slacko 5.6 worked OK. Slacko 5.7 should be the same or better.
Some specific details on what you did would help.
Downloaded iso from where?
Installed how?
To what?
Graphics setup you are using?
Some computer details.
What is it?
Any Slacko 5.6 files on the installed to device?
The things they do not tell you, are usually the clue to solving the problem.
When I was a kid I wanted to be older.... This is not what I expected
YaPI(any iso installer)
When I was a kid I wanted to be older.... This is not what I expected
YaPI(any iso installer)
bad install?
Downloaded in the usual place,can't remember the specific mirror. The p56
files were hidden on a mint partition while I tried the 57, and the installation was on a vfat(i.e., drive c:\ of dos/windows, so not likely the pup locked onto
the 56 files.
I will use the md5 to check for corruption of the downloaded iso, but if the
burner software screwed up, I'm not sure how to check the burned file on the cd.
My preffered installation is to run the cd to generate the sfs,etc,then
thereafter boot from the iso on harddrive(in the vfat partition) using grub4dos; when this would not work for the 57, I did 'full install' to vfat,
booting that from grub4dos. This seemed to work until watching stream for awhile, noticed the problem.
The boot the iso method did and does work with the 56 image, as well as
the last several pups I have used.
Machine is a dell dimension with amd 64, circa '07,not too obsolete.
Let me md5 the iso.
files were hidden on a mint partition while I tried the 57, and the installation was on a vfat(i.e., drive c:\ of dos/windows, so not likely the pup locked onto
the 56 files.
I will use the md5 to check for corruption of the downloaded iso, but if the
burner software screwed up, I'm not sure how to check the burned file on the cd.
My preffered installation is to run the cd to generate the sfs,etc,then
thereafter boot from the iso on harddrive(in the vfat partition) using grub4dos; when this would not work for the 57, I did 'full install' to vfat,
booting that from grub4dos. This seemed to work until watching stream for awhile, noticed the problem.
The boot the iso method did and does work with the 56 image, as well as
the last several pups I have used.
Machine is a dell dimension with amd 64, circa '07,not too obsolete.
Let me md5 the iso.
continued...
Checked the 57 iso with md5,passed;
then, on reflection:
graphics,et al is meaningless because of a glaring fact: grub4dos is completely unaware of such things. Yet,it will boot the 56 and not the 57 iso.
I believe that any bootable iso must have a 'loopback.cfg' file; I did not see
it in the 57 *or* 56 iso's. perhaps it is lurking in 'boot.cat'?
In any case,when trying to boot the 57, grub4dos searches,gives up and
boots the next entry in menu.lst.
Here is the code used in the menu.lst:
title p56(or 7)
fallback 15
find --set-root /images/s56.iso
map /images/s56.iso (0xff) || map --mem /images/s56.iso (0xff)
map --hook
chainloader (0xff)
savedefault --wait=2
Again, the above code boots the 56, but if 56 is changed to 57, it is nogo.
Note I shorten the iso filenames because of all the typing involved(hate
funky filenames).
then, on reflection:
graphics,et al is meaningless because of a glaring fact: grub4dos is completely unaware of such things. Yet,it will boot the 56 and not the 57 iso.
I believe that any bootable iso must have a 'loopback.cfg' file; I did not see
it in the 57 *or* 56 iso's. perhaps it is lurking in 'boot.cat'?
In any case,when trying to boot the 57, grub4dos searches,gives up and
boots the next entry in menu.lst.
Here is the code used in the menu.lst:
title p56(or 7)
fallback 15
find --set-root /images/s56.iso
map /images/s56.iso (0xff) || map --mem /images/s56.iso (0xff)
map --hook
chainloader (0xff)
savedefault --wait=2
Again, the above code boots the 56, but if 56 is changed to 57, it is nogo.
Note I shorten the iso filenames because of all the typing involved(hate
funky filenames).
This can cause problems if the Vfat formatted partition is fragmented.installation was on a vfat(i.e., drive c:\ of dos/windows,
Use Windows to defrag before you install Slacko to it.
You seem to be only trying to boot from the Puppy iso file and not doing an actual install of Puppy.
If the iso files are in different locations I would guess you have one in the proper location, for the boot entry to find, and the other one is not.
Try putting both iso files in the exact same location.
The things they do not tell you, are usually the clue to solving the problem.
When I was a kid I wanted to be older.... This is not what I expected
YaPI(any iso installer)
When I was a kid I wanted to be older.... This is not what I expected
YaPI(any iso installer)
continued
The two iso files,s56.iso and s57.iso are both in the same folder,called images;
the sfs and save files are on c:\, but not in images. When the pup iso boots, it asks for
which pupsave to use, and they are distinguished by their filenames, which I do not alter.
Of course, the 57 never gets this far,since it won't even start to boot; you seem to be suggesting that the 57 iso misfortunately is on a fragmentation line? This is a fascinating
thought, that grub4dos could stumble at this,since again, grub4dos is completely unaware
of any sfs involvement when just beginning to boot.
Nevertheless, I will defragment that partition to see if it changes anything.
the sfs and save files are on c:\, but not in images. When the pup iso boots, it asks for
which pupsave to use, and they are distinguished by their filenames, which I do not alter.
Of course, the 57 never gets this far,since it won't even start to boot; you seem to be suggesting that the 57 iso misfortunately is on a fragmentation line? This is a fascinating
thought, that grub4dos could stumble at this,since again, grub4dos is completely unaware
of any sfs involvement when just beginning to boot.
Nevertheless, I will defragment that partition to see if it changes anything.
Do you get any error message when booting Slacko 5.7 or does it just not do anything?
Copy and paste in Puppy:
In the console terminal that comes with Puppy.
Copy- left click hold and highlight
Paste- middle mouse button click
Also works to copy from terminal and paste to other programs.
Also if you use copy method that comes with other programs you can paste in terminal by middle mouse click.
Copy and paste in Puppy:
In the console terminal that comes with Puppy.
Copy- left click hold and highlight
Paste- middle mouse button click
Also works to copy from terminal and paste to other programs.
Also if you use copy method that comes with other programs you can paste in terminal by middle mouse click.
The things they do not tell you, are usually the clue to solving the problem.
When I was a kid I wanted to be older.... This is not what I expected
YaPI(any iso installer)
When I was a kid I wanted to be older.... This is not what I expected
YaPI(any iso installer)
-
gcmartin
I think the fragmentation may be the problem as is suggested by BigPUP. Seen this before on similar filesystem.
Funny, no one, thus far, has produced a fragmentation checker for ISOs on MS filesystems.
This is a REQUIREMENT for booting directly the ISO with GRUB4DOS.
As well known as this problem is, I wonder if there is a front-end writer which can be told to ONLY write a file, contiguously?
Funny, no one, thus far, has produced a fragmentation checker for ISOs on MS filesystems.
This is a REQUIREMENT for booting directly the ISO with GRUB4DOS.As well known as this problem is, I wonder if there is a front-end writer which can be told to ONLY write a file, contiguously?