woof-CE needs you

News, happenings
Message
Author
User avatar
sc0ttman
Posts: 2812
Joined: Wed 16 Sep 2009, 05:44
Location: UK

trying woof

#1006 Post by sc0ttman »

I've tried to build a 32-bit Slacko 6.9.9.9, using kernel 4.4 (choice number 24 in the Kernel chooser)..

I simply tried to build a Slacko 6.9.9.9 RC3, by using the latest Woof snapshot, with al ldefault options.

I also used an older one from a few weeks back.. Both times I have not been able to boot to X .. I get a 'no screens found message'..

The latest Woof-CE snapshot gave me a 'xorgwizard-automatic not found' error (line 117 of xwin I think), and the second and third builds I did using slightly older Woofs did not have this error message, but they still could not boot to X ..

I tried every option in xorgwizard, and am able to get a desktop on other pups on the same hardware..

Any ideas?
[b][url=https://bit.ly/2KjtxoD]Pkg[/url], [url=https://bit.ly/2U6dzxV]mdsh[/url], [url=https://bit.ly/2G49OE8]Woofy[/url], [url=http://goo.gl/bzBU1]Akita[/url], [url=http://goo.gl/SO5ug]VLC-GTK[/url], [url=https://tiny.cc/c2hnfz]Search[/url][/b]

User avatar
Billtoo
Posts: 3720
Joined: Tue 07 Apr 2009, 13:47
Location: Ontario Canada

#1007 Post by Billtoo »

@sc0ttman

Try the rationalise branch, it's the one that I used last.

User avatar
sc0ttman
Posts: 2812
Joined: Wed 16 Sep 2009, 05:44
Location: UK

#1008 Post by sc0ttman »

Billtoo wrote:@sc0ttman

Try the rationalise branch, it's the one that I used last.
ok will do, cheers
[b][url=https://bit.ly/2KjtxoD]Pkg[/url], [url=https://bit.ly/2U6dzxV]mdsh[/url], [url=https://bit.ly/2G49OE8]Woofy[/url], [url=http://goo.gl/bzBU1]Akita[/url], [url=http://goo.gl/SO5ug]VLC-GTK[/url], [url=https://tiny.cc/c2hnfz]Search[/url][/b]

User avatar
mavrothal
Posts: 3096
Joined: Mon 24 Aug 2009, 18:23

Re: trying woof

#1009 Post by mavrothal »

sc0ttman wrote:I simply tried to build a Slacko 6.9.9.9 RC3, by using the latest Woof snapshot, with al ldefault options.
6.9.9.9 was build with woof 126 commits earlier than the current snapshot.
It shouldn't, but something may have broken the slacko build since.
Try to clone the entire git repo and then

Code: Select all

git checkout 762210b829267e394fe69ae109adf9587dcdf39a #the commit 6.9.9.9 was build from
Or if you do not want to clone the entire git browse to the said commit and download from there.
If this builds OK file a bug in github
BTW, rationalize is just 14 commits behind testing. No other difference. If this works that narrows down the bug a lot.
== [url=http://www.catb.org/esr/faqs/smart-questions.html]Here is how to solve your[/url] [url=https://www.chiark.greenend.org.uk/~sgtatham/bugs.html]Linux problems fast[/url] ==

User avatar
norgo
Posts: 388
Joined: Fri 13 Nov 2015, 17:19
Location: Germany
Contact:

#1010 Post by norgo »

The day before yesterday I built a Slacko 6.9.9.9 RC3 too ( testing branch of 2017-07-31 ) and also chose kernel 4.4.70 PAE

Everything went without problems and Distro is working great.
Thanks for this awesome work.

# inxi -b
System: Host: puppypc28875 Kernel: 4.4.70 i686 (32 bit) Desktop: JWM 2.3.2 Distro: Slacko Puppy 6.9.9.9
Machine: Device: desktop Mobo: ASRock model: H87 Pro4 serial: M80-xxxxxxxxxxx
BIOS: American Megatrends v: P1.90 date: 12/06/2013
CPU: Quad core Intel Core i7-4770S (-HT-MCP-) speed/max: 800/3101 MHz
Graphics: Card: Intel Xeon E3-1200 v3/4th Gen Core Processor Integrated Graphics Controller
Display Server: X.org 1.18.3 driver: intel tty size: 163x52 Advanced Data: N/A for root
Network: Card: Intel Ethernet Connection I217-V driver: e1000e
Drives: HDD Total Size: 2000.4GB (0.1% used)
Info: Processes: 190 Uptime: 1:17 Memory: 505.5/15863.1MB Client: Shell (bash) inxi: 2.3.8
Attachments
screenshot_800x500.jpg
Slacko 700 RC3
(91.39 KiB) Downloaded 470 times

User avatar
Billtoo
Posts: 3720
Joined: Tue 07 Apr 2009, 13:47
Location: Ontario Canada

#1011 Post by Billtoo »

I did a fresh install of woof-CE then did a build using the rationalise branch.
I get the same result as sc0ttman, x won't start.

EDIT:
Last night I did a build on another pc where woof-CE was installed jul15th,using the rationalise branch.
Boots to the desktop no problem.

Here's the build that was done on the jul15 woof-CE install,
rationalise branch:

# inxi -b
System: Host: puppypc12281 Kernel: 4.4.70 i686 (32 bit) Desktop: JWM 2.3.2 Distro: Slacko Puppy 6.9.9.9
Machine: Device: desktop Mobo: Gateway model: FX6860 serial: 109726660000629
BIOS: American Megatrends v: P01-A3 date: 04/19/2011
CPU: Quad core Intel Core i7-2600 (-HT-MCP-) speed/max: 1600/3401 MHz
Graphics: Card: NVIDIA GF110 [GeForce GTX 560 Ti OEM]
Display Server: X.org 1.18.3 driver: nvidia tty size: 124x27 Advanced Data: N/A for root
Network: Card-1: Ralink RT3090 Wireless 802.11n 1T/1R PCIe driver: rt2800pci
Card-2: Realtek RTL8111/8168/8411 PCI Express Gigabit Ethernet Controller driver: r8169
Drives: HDD Total Size: 2031.9GB (0.0% used)
Info: Processes: 220 Uptime: 3 min Memory: 193.4/16192.6MB Client: Shell (bash) inxi: 2.3.8
#
Attachments
jul15woof-CE.jpg
(42.47 KiB) Downloaded 418 times

User avatar
mavrothal
Posts: 3096
Joined: Mon 24 Aug 2009, 18:23

#1012 Post by mavrothal »

DISTRO_SPECS should show exactly which woof branch and commit a puppy is build from. This info (assuming no "manual" post processing) is much more specific than date or commit number, and more helpful when try to track down potential problems.
== [url=http://www.catb.org/esr/faqs/smart-questions.html]Here is how to solve your[/url] [url=https://www.chiark.greenend.org.uk/~sgtatham/bugs.html]Linux problems fast[/url] ==

User avatar
Billtoo
Posts: 3720
Joined: Tue 07 Apr 2009, 13:47
Location: Ontario Canada

#1013 Post by Billtoo »

mavrothal wrote:DISTRO_SPECS should show exactly which woof branch and commit a puppy is build from. This info (assuming no "manual" post processing) is much more specific than date or commit number, and more helpful when try to track down potential problems.
This is the jul15th woof-CE install:

#One or more words that identify this distribution:
DISTRO_NAME='Slacko Puppy'
#version number of this distribution:
DISTRO_VERSION=6.9.9.9
#The distro whose binary packages were used to build this distribution:
DISTRO_BINARY_COMPAT='slackware'
#Prefix for some filenames: exs: slackosave.2fs, slacko-6.9.9.9.sfs
DISTRO_FILE_PREFIX='slacko'
#The version of the distro whose binary packages were used to build this distro:
DISTRO_COMPAT_VERSION='14.2'
#the kernel pet package used:
DISTRO_KERNEL_PET='Huge_Kernel'
DISTRO_XORG_AUTO='yes'
DISTRO_DB_SUBNAME='slacko14.2'
DISTRO_TARGETARCH='x86'
BUILD_FROM_WOOF='rationalise;7a95a9e;2017-06-28 19:41:26 +1000'

*******************************************************************************************

This is from the woof-CE install done this morning, X failed to start.

#One or more words that identify this distribution:
DISTRO_NAME='Slacko Puppy'
#version number of this distribution:
DISTRO_VERSION=6.9.9.9
#The distro whose binary packages were used to build this distribution:
DISTRO_BINARY_COMPAT='slackware'
#Prefix for some filenames: exs: slackosave.2fs, slacko-6.9.9.9.sfs
DISTRO_FILE_PREFIX='slacko'
#The version of the distro whose binary packages were used to build this distro:
DISTRO_COMPAT_VERSION='14.2'
#the kernel pet package used:
DISTRO_KERNEL_PET='Huge_Kernel'
DISTRO_XORG_AUTO='yes'
DISTRO_DB_SUBNAME='slacko14.2'
DISTRO_TARGETARCH='x86'
BUILD_FROM_WOOF='rationalise;bdab886;2017-07-29 17:54:31 +0800'

User avatar
mavrothal
Posts: 3096
Joined: Mon 24 Aug 2009, 18:23

#1014 Post by mavrothal »

It would appear that there are several X related commits and also several package template related commits between the "good" and the "bad" builds.
If you have the opportunity you may want to try building from ed23309c and/or ffd2229 and hopefully narrow down the range a bit more.
== [url=http://www.catb.org/esr/faqs/smart-questions.html]Here is how to solve your[/url] [url=https://www.chiark.greenend.org.uk/~sgtatham/bugs.html]Linux problems fast[/url] ==

User avatar
norgo
Posts: 388
Joined: Fri 13 Nov 2015, 17:19
Location: Germany
Contact:

#1015 Post by norgo »

Here the DISTRO_SPECS of my Slacko:

#One or more words that identify this distribution:
DISTRO_NAME='Slacko Puppy'
#version number of this distribution:
DISTRO_VERSION=6.9.9.9
#The distro whose binary packages were used to build this distribution:
DISTRO_BINARY_COMPAT='slackware'
#Prefix for some filenames: exs: slackosave.2fs, slacko-6.9.9.9.sfs
DISTRO_FILE_PREFIX='slacko'
#The version of the distro whose binary packages were used to build this distro:
DISTRO_COMPAT_VERSION='14.2'
#the kernel pet package used:
DISTRO_KERNEL_PET='Huge_Kernel'
DISTRO_XORG_AUTO='yes'
DISTRO_DB_SUBNAME='slacko14.2'
DISTRO_TARGETARCH='x86'
BUILD_FROM_WOOF='testing;bdab886;2017-07-29 17:54:31 +0800'

User avatar
Billtoo
Posts: 3720
Joined: Tue 07 Apr 2009, 13:47
Location: Ontario Canada

#1016 Post by Billtoo »

I did a new install of woof-CE testing branch and did a new build, it
has the same problem as the rationalise branch in that X won't start.

#One or more words that identify this distribution:
DISTRO_NAME='Slacko Puppy'
#version number of this distribution:
DISTRO_VERSION=6.9.9.9
#The distro whose binary packages were used to build this distribution:
DISTRO_BINARY_COMPAT='slackware'
#Prefix for some filenames: exs: slackosave.2fs, slacko-6.9.9.9.sfs
DISTRO_FILE_PREFIX='slacko'
#The version of the distro whose binary packages were used to build this distro:
DISTRO_COMPAT_VERSION='14.2'
#the kernel pet package used:
DISTRO_KERNEL_PET='Huge_Kernel'
DISTRO_XORG_AUTO='yes'
DISTRO_DB_SUBNAME='slacko14.2'
DISTRO_TARGETARCH='x86'
BUILD_FROM_WOOF='testing;6e9bb39;2017-07-31 17:43:50 +0800'

So I did a fresh install of woof-CE with both testing and rationalise
branchs and neither one will built a working slacko 32bit.

Oh my :(

User avatar
norgo
Posts: 388
Joined: Fri 13 Nov 2015, 17:19
Location: Germany
Contact:

#1017 Post by norgo »

@Billtoo

when I understand this correctly, your used rationalise and my used testing branch became merged and are absolutely identical

BUILD_FROM_WOOF='rationalise;bdab886;2017-07-29 17:54:31 +0800'
BUILD_FROM_WOOF='testing;bdab886;2017-07-29 17:54:31 +0800'

I remember that a while ago the 20-intel.conf file has been added to /etc/X11/xorg.conf.d

Driver and acceleration method are defined for card0

Your computer has two graphics cards ( intel and nvidia )
Which card is card0 and which is card1 ?
In case that nvidia is card0, this could become a problem.

Could you delete /etc/X11/xorg.conf.d/20-intel.conf and try to boot for test please.
It's only a guess, but could be the reason.

User avatar
Billtoo
Posts: 3720
Joined: Tue 07 Apr 2009, 13:47
Location: Ontario Canada

#1018 Post by Billtoo »

norgo wrote:@Billtoo

when I understand this correctly, your used rationalise and my used testing branch became merged and are absolutely identical

BUILD_FROM_WOOF='rationalise;bdab886;2017-07-29 17:54:31 +0800'
BUILD_FROM_WOOF='testing;bdab886;2017-07-29 17:54:31 +0800'

I remember that a while ago the 20-intel.conf file has been added to /etc/X11/xorg.conf.d

Driver and acceleration method are defined for card0

Your computer has two graphics cards ( intel and nvidia )
Which card is card0 and which is card1 ?
In case that nvidia is card0, this could become a problem.

Could you delete /etc/X11/xorg.conf.d/20-intel.conf and try to boot for test please.
It's only a guess, but could be the reason.
Hi,

I installed the latest woof-CE (rationalise branch) this morning to a new work directory on
my Gateway i7 hard drive, did a build and X wouldn't run.

The Gateway only has 1 graphics card as far as I know, Nvidia 560 ti.
I downloaded the kernel source sfs from ibiblio and the proprietary
driver from the Nvidia site and compiled it, have to blacklist the
nouveau kernel module and reboot first.

**********************************************************************

I installed the latest woof-CE (testing branch) this afternoon to a new
work directory on my HP Phenom II, AMD 6 core processor, did a build and X wouldn't run.

The rationalise branch install that did work on the Gateway was built
in the jul15 work directory on the HP hard drive (different partition too)

It seems that both branchs were updated on the same day, neither will
build a working 32 bit slacko.

Bill

User avatar
norgo
Posts: 388
Joined: Fri 13 Nov 2015, 17:19
Location: Germany
Contact:

#1019 Post by norgo »

I used the compare feature at github page and got the message nothing to compare, because both are identical.
In my case this version is working like a charm.

I'm quite sure that your i7 has a graphics chip included ;-)
Of course I don't know the hardware of your HP computer.
As I mentioned, it's only a guess and actual easy to test.

greetings

User avatar
mavrothal
Posts: 3096
Joined: Mon 24 Aug 2009, 18:23

#1020 Post by mavrothal »

If X tried to start and failed should produce a /var/log/Xorg.0.log file. Also the /initrd/tmp/dmesg.txt file could be informative and maybe the /initrd/tmp/bootinit.log file
== [url=http://www.catb.org/esr/faqs/smart-questions.html]Here is how to solve your[/url] [url=https://www.chiark.greenend.org.uk/~sgtatham/bugs.html]Linux problems fast[/url] ==

User avatar
Billtoo
Posts: 3720
Joined: Tue 07 Apr 2009, 13:47
Location: Ontario Canada

#1021 Post by Billtoo »

mavrothal wrote:If X tried to start and failed should produce a /var/log/Xorg.0.log file. Also the /initrd/tmp/dmesg.txt file could be informative and maybe the /initrd/tmp/bootinit.log file
@norgo had success with his testing branch iso so I burned the one from
my new woof-CE testing branch (yesterday afternoon) to a DVD and tried
it on a pc with intel graphics (X wouldn't start on my HP ATI Radeon)
and it works.
I'm booting from the DVD with a save file on the hard drive.

# inxi -bw
System: Host: puppypc27878 Kernel: 4.4.70 i686 (32 bit) Desktop: JWM 2.3.2 Distro: Slacko Puppy 6.9.9.9
Machine: Device: desktop Mobo: Acer model: Aspire X3950 serial: U02C120500059
BIOS: American Megatrends v: P01-A3 date: 05/05/2010
CPU: Dual core Intel Core i3 540 (-HT-MCP-) speed/max: 1333/3067 MHz
Graphics: Card: Intel Core Processor Integrated Graphics Controller
Display Server: X.org 1.18.3 driver: intel tty size: 144x40 Advanced Data: N/A for root
Network: Card: Realtek RTL8111/8168/8411 PCI Express Gigabit Ethernet Controller driver: r8169
Drives: HDD Total Size: 532.1GB (4.0% used)
Weather: Conditions: 68 F (20 C) - Partly Cloudy Time: August 3, 8:46 AM EDT
Info: Processes: 179 Uptime: 3 min Memory: 288.0/5997.2MB Client: Shell (bash) inxi: 2.3.8
#
I'll try booting the DVD on the Gateway which has Nvidia graphics and
see how that goes.

EDIT: The DVD boots to the desktop on the Gateway but the resolution is wrong and the mouse is dead,ctrl-alt-backspace does nothing.

So recent commits have caused problems with Radeon and Nvidia graphics on my hardware.
Attachments
screenshot.jpg
(31.78 KiB) Downloaded 1367 times

User avatar
sc0ttman
Posts: 2812
Joined: Wed 16 Sep 2009, 05:44
Location: UK

#1022 Post by sc0ttman »

Have built a slacko pup (32-bit, kernel 4.4, which is number 24 in the list during woof build)

It boots from CD and USB, all the way to desktop on a Dell Optiplex GX-something, which has on-board Intel gfx, and also boots to desktop on my main PC (with AMD radeon 7750 gfx) ..

Am using it now.. Works very nicely..

This is from the /etc/DISTRO_SPECS

Code: Select all

BUILD_FROM_WOOF='testing;6e9bb39;2017-07-31 17:43:50 +0800'
inxi - bw

Code: Select all

System:    Host: puppypc28490 Kernel: 4.4.70 i686 (32 bit) Desktop: JWM 2.3.2 Distro: Slak Puppy 6.9.11
Machine:   Device: desktop Mobo: ASRock model: FM2A75 Pro4 serial: E80-37025800032
           BIOS: American Megatrends v: P2.40 date: 07/11/2013
CPU:       Quad core AMD Athlon X4 750K (-MCP-) speed/max: 1400/3400 MHz
Graphics:  Card: Advanced Micro Devices [AMD/ATI] Cape Verde PRO [Radeon HD 7750/8740 / R7 250E]
           Display Server: X.org 1.18.3 drivers: ati,radeon (unloaded: modesetting,fbdev,vesa)
           tty size: 211x64 Advanced Data: N/A for root
Network:   Card: Realtek RTL8111/8168/8411 PCI Express Gigabit Ethernet Controller driver: r8169
Drives:    HDD Total Size: 2016.6GB (4.9% used)
Weather:   Conditions: 68 F (20 C) - Mostly Cloudy Time: August 3, 3:58 PM BST
Info:      Processes: 190 Uptime: 1:26 Memory: 563.8/16171.5MB Client: Shell (bash) inxi: 2.3.8 
For reference, the previous errors (now gone in 6e9bb39?) were "missing xorgwizard-automatic, line 113 of xwin" in one very recent build, and missing "FreeSans" font errors in a slightly older one... I had those errors on both machines mentioned above, and in a VM.

... Now some general observations..

1. Is the missing fonts message that prevented my desktop loading up (in previous builds) related to not including pTheme?

2. JWM is crap at working out 2 monitors, and moving them around is a real pain - compared to the drag and drop UI that Xfce provides.. Any way round this? Zarfy, maybe?

3. Does the Universal Pup Installer insist on overwriting the MBR of every drive/disk that uses GRUB? (or is it just me?)... Seems every time I try to use the Universal Installer, it insists I replace my MBR with mbr.bin (or other).. Can the Universal installer not work out I have a working GRUB, just leave the MBR?

4. IIRC, the Grub4DosConfig app doesn't backup the menu-adv.lst file, only the menu.lst file..

5. Where is the documentation about adding new petbuilds and pet packages to Woof? I want to create a new branch and make it build an Xfce pup (ideally... baby steps)..

6. I've noticed that none of the following keys works as they should in Urxvt: Crtl-Left, Ctrl-Right, Home key, End key ... Should this be fixed in /etc/profile, or ~/.bashrc? i'm pretty sure i've got a puppy bashrc with all these fixes in it somewhere if anyone would prefer them working in woof-built pups..

7. How does having an Fdrv and a Ydv affect the zdrv-cutter thing? .. It that still a thing? Can't find it in my newly woofed pup..
[b][url=https://bit.ly/2KjtxoD]Pkg[/url], [url=https://bit.ly/2U6dzxV]mdsh[/url], [url=https://bit.ly/2G49OE8]Woofy[/url], [url=http://goo.gl/bzBU1]Akita[/url], [url=http://goo.gl/SO5ug]VLC-GTK[/url], [url=https://tiny.cc/c2hnfz]Search[/url][/b]

User avatar
Billtoo
Posts: 3720
Joined: Tue 07 Apr 2009, 13:47
Location: Ontario Canada

woof-CE needs you

#1023 Post by Billtoo »

I did a fresh install of woof-CE testing branch then a new build:

# inxi -bw
System: Host: puppypc4675 Kernel: 4.4.80-pae i686 (32 bit) Desktop: JWM 2.3.2 Distro: Slacko Puppy 6.9.9.9
Machine: Device: laptop System: Acer product: Aspire 7740 v: Rev serial: LXPNX02012004098672000
Mobo: Acer model: Aspire 7740 v: Rev serial: LXPNX02012004098672000
BIOS: Phoenix v: V1.15 date: 12/25/2009
Battery BAT0: charge: 44.0 Wh 100.0% condition: 44.0/44.0 Wh (100%)
CPU: Dual core Intel Core i5 M 430 (-HT-MCP-) speed/max: 1199/2267 MHz
Graphics: Card: Advanced Micro Devices [AMD/ATI] Park [Mobility Radeon HD 5430/5450/5470]
Display Server: X.org 1.18.3 drivers: ati,radeon (unloaded: modesetting,fbdev,vesa)
tty size: 131x37 Advanced Data: N/A for root
Network: Card-1: Broadcom Limited NetLink BCM57780 Gigabit Ethernet PCIe driver: tg3
Card-2: Qualcomm Atheros AR928X Wireless Network Adapter (PCI-Express) driver: ath9k
Drives: HDD Total Size: 540.0GB (1.9% used)
Weather: Conditions: 68 F (20 C) - Overcast Time: August 10, 9:25 AM EDT
Info: Processes: 187 Uptime: 1:22 Memory: 222.1/3902.9MB Client: Shell (bash) inxi: 2.3.8
#

Running from a 32gb SDHC card on Acer laptop.

Works good, thanks for the fix.
******************************************************************
EDIT:
Same woof-CE version,new build:

# inxi -bw
System: Host: puppypc12471 Kernel: 4.4.83-pae i686 (32 bit) Desktop: JWM 2.3.2 Distro: Slacko Puppy 6.9.9.9
Machine: Device: desktop System: ACER product: Aspire M5620 v: R01-A4 serial: PTS860X0348050CF642700
Mobo: ACER model: G33T-AM v: 1.0 serial: 00000000 BIOS: American Megatrends v: R01-A4 date: 12/19/2007
CPU: Quad core Intel Core2 Quad Q6600 (-MCP-) speed/max: 1603/2403 MHz
Graphics: Card: NVIDIA GF108 [GeForce GT 430]
Display Server: X.org 1.18.3 driver: nvidia tty size: 163x30 Advanced Data: N/A for root
Network: Card: Intel 82566DC-2 Gigabit Network Connection driver: e1000e
Drives: HDD Total Size: 31.9GB (10.3% used)
Weather: Conditions: 75 F (24 C) - Mostly Cloudy Time: August 17, 11:49 AM EDT
Info: Processes: 193 Uptime: 51 min Memory: 690.0/8097.6MB Client: Shell (bash) inxi: 2.3.8
#

Works well so far.
Attachments
screenshotaug17.jpg
(77.05 KiB) Downloaded 919 times
screenshot.jpg
(94.62 KiB) Downloaded 1108 times
Last edited by Billtoo on Thu 17 Aug 2017, 15:56, edited 1 time in total.

Sailor Enceladus
Posts: 1543
Joined: Mon 22 Feb 2016, 19:43

#1024 Post by Sailor Enceladus »

sc0ttman wrote:6. I've noticed that none of the following keys works as they should in Urxvt: Crtl-Left, Ctrl-Right, Home key, End key ... Should this be fixed in /etc/profile, or ~/.bashrc? i'm pretty sure i've got a puppy bashrc with all these fixes in it somewhere if anyone would prefer them working in woof-built pups..
If Ctrl-Left and Ctrl-Right are the keys that switch you to a different virtual window I've always found that shortcut just annoying. I'll be playing a game and the desktop will randomly switch to a different one where my game isn't on instead of doing what it's suppose to inside the game. I think it was Tahrpup that had this issue, as I remember the "pink square" moving left and right when my screen disappeared. Might have been Alt-Left/Right though, haven't experienced the issue for a while now.

belham2
Posts: 1715
Joined: Mon 15 Aug 2016, 22:47

#1025 Post by belham2 »

The Slacko64-6.9.9.9 frugal-install the I use a few times a week has started to display helter-skelter behavior (freezing screens, programs randomly refusing to open, etc) . Don't understand as everything was running great for a few months, with no new add-ons (or anything) have been applied to this latest release. Only thing that has changed is that I like to plug the USB drive that has all these frugal-installs into many of my different machines here-----and this new Slacko64-6.9.9.9 does not like this one bit.

Sure is a stark contrast on things when I throw Sailor E's slacko 5.7 build (into any machine) and everything just stinking runs like wildfire, no matter what I've thrown at it, I can't even get it to hiccup (and I've been doing crazy qt stuff with it, lol). Maybe I need newer systems to reliably run all of Micko's later creations; makes me sad :cry: Wife won't be having any of that soon, unfortunately. My newest hardware is 6 yrs old (i3 laptop), and the others are 8-19 yrs old (the oldest being a Pentium 2.0 I try to keep going, lol, and it does have a 1GB of ram, in its defense of staying relevant).

Post Reply