Hi all. Been way too long since I've been around and helped with any testing, but I'm trying out Tahr 6.06 and have run across something that I haven't seen mentioned in this thread yet.

I'm working with a painfully slow HP 2000 laptop. Hard drive is NTFS (for Win 10). It's not my machine, so I'm not doing a frugal install or anything that would cause a permanent change - I'm simply booting from CD and saving a save file to the hard drive, which I will move off of the machine later.

I created a "/tahrpup606" folder to hold all the Puppy stuff for easy transfer. The catch is that the boot process doesn't find the save files or the main SFS files that I put in that folder.

When I copy the save file and SFS files to the partition's top level, it finds and loads them perfectly fine, but it doesn't seem to see them one layer deep in the /tahrpup606 folder.

X doesn't immediately start. If I wait a couple minutes, the X dialogue appears and I can type xwin and the normal screen appears. I tried replacing the etc/X11/xorg.conf file with the one from my original Tahr 6.0CE, but it acts the same.

This is a Lenovo Thinkpad with 2x AMD A6-5350M processor and Radeon HD 8450G video card.

Installed on hard drive partition formatted what?
Using what boot loader?
Are you using the save from the Tahrpup 6.0CE?_________________I have found, in trying to help people, that 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

Upon further thought I decided the format of the save file wouldn't matter, I have the option in Grub to load without the save file, and it loads the same. I changed it anyway to ext2, 2 gigs.
I went into BIOS and I changed startup from legacy bios to UEFI. No difference.
It's not a horrible thing to live with- I'll survive. I do like it otherwise.

The hard drive is formatted as ntfs - the laptop is shared with Windows7

.
Any drive that is also used by Windows.

Before installing Puppy

Need to run Windows defrag and chkdsk programs on the ntfs partition to defrag it and check and correct any errors in the ntfs file system.

A fragmented file system can cause all kinds of problems with Puppy installs._________________I have found, in trying to help people, that 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

The hard drive is formatted as ntfs - the laptop is shared with Windows7

.
Any drive that is also used by Windows.

Before installing Puppy

Need to run Windows defrag and chkdsk programs on the ntfs partition to defrag it and check and correct any errors in the ntfs file system.

A fragmented file system can cause all kinds of problems with Puppy installs.

For a good defragger, I recommend "Defraggler" by Piriform. The included Windows defragger does a poor job, in my opinion. Go to the "builds" page and get the "portable version" (if you come in from the front, you have to wade through several pages to reach "builds", at the bottom of one of the pages)

BTW, I would not generally recommend that you install a frugal Puppy on a Win10 partition. Win10 is hostile to other systems -- my observation is that every time Puppy "modifies" the hard drive, such as copying a file onto it, Win10 decides that it absolutely must do a FULL SCAN of the hard drive, then "fixes" the added file by removing it. I could see it deciding to "fix" your save file, and deleting it...for your "convenience"...

Windows7 seemed to tolerate it - though I actually booted from a USB, which then pointed to the HDD for the system and save files (I didn't want to mess with the boot sequence, which it trickier than on XP systems -- but if you want to do so, see Lin'N'Win for instructions -- I run Lin'N'Win on all of my XP and older machines)

Incidentally, on WinXP and older, it's easier to do the modifications from Linux (you don't have to unhide files, etc). Drop the files in, edit the boot loader file, and make sure that your menu.lst points to the correct locations.

On my Win10, I run my Puppy on an external USB HDD, velcroed to the back of the lid (for the reasons explained above). When I want to run Win10, I unplug the USB. When I want Puppy, I make sure that it boots from the USB...

If you just want to tinker with the machine, without permanent mods, install to a flash drive or USB HDD. Change to BIOS to look at CD and USB first._________________Add swapfileWellMinded Search

I have tahr6.0.2 32bit on a 10 year old intel dualcore desktop. I rebuild it to my liking, it does not look much like tahr anymore

For a year now, I have an ideapad, i5 quadcore, dual graphic cards (intel/nvidia) with windoze10. I don't use windows a lot. I run a collection of modern Puppies on it, kernel at least 4.1.
Now I got the idea to try tahrpup64-6.0.6 on it. With the old 3.14 kernel it does not get to X at all.
So I decided to switch the kernel with the recent 4.9.58 kernel from xenialpup. Now I do get to X! At first sight of the tahr desktop with its beautiful icons, my heart skipped a beat; I recognised again what wonderful build Tahr is.
But there is a little problem: there seems to be some "screen tearing". It appears/disappears in rox or other windows (the browser) when I resize them or scroll. In pupsysinfo the top bar with the menus is black until I click in it. The tearing is not static, it changes (blocks, stripes, black surfaces... ) and it can disappear when I click on another window or on the menu button.
Is there something I can do?

I also noticed that the icons in the applet tray flicker from time to time. I don't think that is normal behaviour?

You cannot post new topics in this forumYou cannot reply to topics in this forumYou cannot edit your posts in this forumYou cannot delete your posts in this forumYou cannot vote in polls in this forumYou cannot attach files in this forumYou can download files in this forum