Free Dvd Boot Ps2 3.11 Download _BEST_
Terresa Beckley
I have tried to flash newest v3.11 BIOS with AGESA 1.1.0.0 Patch C and it won't boot if I try to enable XMP. Board has some diagnostic LEDs, and ones for CPU and DRAM are lit red when it not boot. Im not fully sure about LEDs, because they can be seen clearly in my case.
I have a 486 PC, 16mb ram with a DX4/75 (though clocked at 100) with Windows 3.11 and DOS6.22 installed on a 2gb CF card (running EZ-BIOS to overcome the size limitations). I'm thinking about getting Windows 95 installed and wondering if there is a "safe" and reliable way to dual boot my setup. Without destroying anything. If its worth doing at all.
After the installation, Windows 95 will boot by default. If you want to change to MS-DOS, press F8 when the message Starting Windows appears and select "Previous operating system" or something like that and you'll boot onto MS-DOS.
I have a custom autoexec/config files at the moment for my current build so I can boot up DOS with various drivers/settings installed or into Windows 3x etc. So I def want to keep that, and perhaps build on it with other options. I'll keep a backup of them anyway.
So, if I'm using this floppy image in DOSBox, does it require that I have a CD image mounted using DOSBox's imgmount command or a CD in my physical drive when I mount it using DOSBox's mount command? Because when I run "boot -l a" after mounting this floppy image, I get:
Error: No CD-ROM drives detected at all.
Error: Device driver aborts loading.
and then the process just refuses to do anything else.
Strange, DOS 7.x (aka Win9x) files instead of the MS-DOS 6.22 ones) i.e. NATIVE FAT32 access, should NOT be able to load the Win3.x GUI unless 3Xstart is loaded.....but maybe this applies to 3.1 and not to 3.11...
5.11 Tactical Men's Boots are crafted to cater to the demanding needs of military personnel, law enforcement officers, and outdoor enthusiasts. These high-performance boots are designed with functionality, durability, and agility in mind, making them the ideal companion for those who require top-quality footwear in any situation. From patrol duty to deployment in challenging environments, 5.11 Tactical Men's Boots offer the perfect mix of ankle support, traction, and responsiveness. The water-resistant suede leather and air mesh nylon construction make our tactical boots lightweight and offer excellent load management. The 5.11 Shock Mitigation System provides enhanced kinetic absorption and rebound, ensuring optimal stamina, stability, and balance. Additional features like impact cushioning, high-traction soles, and strategically placed knife pockets make these boots mission-ready at all times. Available in 6-inch and 8-inch variants, our tactical boots come in various styles, including side zip boots, mid boot styles, and waterproof options. Select the perfect pair for your mission requirements, and trust the innovative engineering, modern materials, and commitment to quality behind 5.11 Tactical Boots.
Can you dual boot Windows 98 and Windows 3.11? I have a customer that has a program, Terminal for CNC Machines that needs Windows 3.11 to function correctly. I would like to know if I can install the hard drive with Windows 3.11 and the Terminal program with the hard drive with Windows 98 installed. Your quick response would be appreciated. Thank you Teri08
I've been trying to get Python 3.11 installed on Unraid 6.11 or 6.12. I looked around for pre-compiled TXZ packages, but only found 3.9.x packages from @dlandon in and @EUGENI_CAT in -NerdTools/blob/main/packages/6.11/python3-3.9.16-x86_64-1.txz
However, I've had some issues after installing this custom-built Python. I bundled Pip into this install since that's supported with a makefile flag, but I started seeing "Can't connect to HTTPS URL because the SSL module is not available." after rebooting Unraid. I suspect this is because the SSL package and system libraries were installed during compilation, so Python doesn't reference its internal SSL library and instead uses the system library, which after an Unraid reboot no longer exists.
I've seen a couple other issues along this line as well.
I'm hoping someone here is aware of an Unraid-compatible Python 3.11 TXZ file, or a SlackBuild file that could get Python compiled and functional on Unraid. Or if someone here simply has more experience with compiling/SlackBuild/makefiles on Unraid, maybe that would also work.
Starting with Python 3.10, OpenSSL 1.1.1 or newer is required -0644/ which means the OpenSSL 1.1 installed by default in Unraid 6.12.3 does not meet the requirements. In other words, using Python 3.10 or newer will require OpenSSL to also be installed as a prerequisite. I got OpenSSL 3.1.2 from -current/slackware64/n/openssl-3.1.2-x86_64-1.txz and added it to the /boot/extra/ directory to install at boot.
I also spent a bunch of time working through the different settings and libraries needed to configure and build/compile Python 3.11.4 on Unraid. I eventually succeeded, and am happy to share the 3.11.4 TXZ file. I put this in the /boot/extra/ directory alongside OpenSSL and am happy to report that Python seems to be working for my needs. I included Pip in the TXZ as well, so Pip will install automatically next to Python and does not need a separate package to install
My required package dependency for building steps
- gcc -current/slackware64/d/gcc-13.2.0-x86_64-1.txz and `installpkg gcc-13.2.0-x86_64-1.txz ` to fix `configure: error: no acceptable C compiler found in $PATH`
- binutils -current/slackware64/d/binutils-2.41-x86_64-1.txz to fix `configure: error: C compiler cannot create executables` which stems from `gcc: fatal error: cannot execute 'as': execvp: No such file or directory` -error-cannot-execute-as-execvp-no-such-file-or-directory
- glibc -current/slackware64/l/glibc-2.37-x86_64-2.txz to fix `configure: error: C compiler cannot create executables` with sub-error `/ld: cannot find crt1.o: No such file or directory`
- kernel-headers -current/slackware64/d/kernel-headers-6.1.42-x86-1.txz to fix `C preprocessor "/lib/cpp" fails sanity check` with sub-error `linux/limits.h: No such file or directory`
- **Everything above here is the minimal set needed to get `./configure` running end to end**
- make -current/slackware64/d/make-4.4.1-x86_64-1.txz obviously just to run make
- guile -current/slackware64/d/guile-3.0.9-x86_64-1.txz to fix the make-time error `make: error while loading shared libraries: libguile-3.0.so.1: cannot open shared object file: No such file or directory`
- gc -current/slackware64/l/gc-8.2.4-x86_64-1.txz to fix the make-time error `make: error while loading shared libraries: libgc.so.1: cannot open shared object file: No such file or directory`
- zlib -current/slackware64/l/zlib-1.2.13-x86_64-1.txz RIP after 45m of compiling I saw an error `zipimport.ZipImportError: can't decompress data; zlib not available`
- libffi -current/slackware64/l/libffi-3.4.4-x86_64-1.txz to fix compilation error `Failed to build these modules: _ctypes` and `_ctypes.c:118:10: fatal error: ffi.h: No such file or directory`
- openssl (not openssl11, which corresponds to 1.1 and not the 3.x of normal openssl) -current/slackware64/n/openssl-3.1.1-x86_64-1.txz to let `./configure` know that SSL exists so that hopefully Python builds the SSL module `checking for openssl/ssl.h in /usr... yes / checking whether compiling and linking against OpenSSL works... yes`
- I see `/usr/bin/openssl` and `/usr/lib64/libevent_openssl.so` and `/usr/lib64/libssl.so` seem to exist on the test Unraid, so maybe it's safe to assume it's available by default? I suspect pkg-config will aid in detecting that it's available
- Nope, I see `checking whether compiling and linking against OpenSSL works... no` when running `/configure`
- Yeah, even when running make I see the same `Could not build the ssl module! Python requires a OpenSSL 1.1.1 or newer` error
- I see that `./configure` has a log line `checking for stdlib extension module _ssl... missing` which makes me suspect that SSL won't be built into this Python package installer, and thus pip is going to fail once I get to that point. I bet I could get around that by installing SSL using the instructions from earlier, but then I suspect it won't really be bundled and will instead just look to the system for an SSL implementation. That said, I wonder if I could install pkg-config AND SSL and set the -with-openssl-rpath `--with-openssl-rpath=auto` flag during configuration and then it would just use whatever SSL is available? The alternative is to just build this, realize SSL is missing, install the SSL package as well, and call it a day. I think it should technically be fine if the python installer also depends on SSL
- pkg-config to resolve a general compiler warning -current/slackware64/d/pkg-config-0.29.2-x86_64-4.txz that `WARNING: pkg-config is missing. Some dependencies may not be detected correctly.`
- bzip2 -current/slackware64/a/bzip2-1.0.8-x86_64-3.txz to fix `checking for stdlib extension module _bz2... missing` in the `./configure`
- xz -current/slackware64/a/xz-5.4.3-x86_64-1.txz to fix to fix `checking for stdlib extension module _lzma... missing` in the `./configure`
- gdbm -current/slackware64/l/gdbm-1.23-x86_64-1.txz to fix `checking for stdlib extension module _gdbm... missing` in the `./configure`
- ncurses -current/slackware64/l/ncurses-6.4_20230610-x86_64-1.txz to fix failed compilation of the `_ncurses` module
**My steps**
- Download python 3 source in xz format to `/boot/buildPython/Python-3.11.4.tar.xz`
- Create a temp directory to do work in, and move there: `rm -rf /tmp/buildPython exit 0 && mkdir /tmp/buildPython && cd /tmp/buildPython`
- Install the dependencies needed to run `./configure` and `make` in `/boot/buildPython`
- Extract the Python source to the temp directory `tar xf /boot/buildPython/Python-3.11.4.tar.xz` which creates a subdirectory `/tmp/buildPython/Python-3.11.4/`
- Move into that subdirectory `cd /tmp/buildPython/Python-3.11.4/`
- Try to run `./configure --build=x86_64-slackware-linux --with-ensurepip=upgrade --prefix=/usr --libdir=/usr/lib64 --with-platlibdir=lib64 --enable-optimizations --with-lto --with-pkg-config=yes --disable-test-modules --without-static-libpython`
- Run make with multiple jobs (assuming multiple CPUs) to compile faster: `make -j6`
- Clear and create the directory that `make install` will output into `rm -rf /tmp/package-python-make-output exit 0 && mkdir -p /tmp/package-python-make-output`
- Run make with `make install DESTDIR=/tmp/package-python-make-output`
- Now remove some of the files in `/tmp/package-python-make-output` that should not be packaged:
- `cd /tmp/package-python-make-output/`
- `find . \( -name '*.exe' -o -name '*.bat' \) -exec rm -f '' \+` to remove windows stuff
- `find . -type d -exec chmod 755 "" \+` to update permissions
- `find . -perm 640 -exec chmod 644 "" \+`
- `find . -perm 750 -exec chmod 755 "" \+`
- `find . -print0 xargs -0 file grep -e "executable" -e "shared object" grep ELF cut -f 1 -d : xargs strip --strip-unneeded 2> /dev/null true` I have no idea what this does but it seemed to find a couple files such as `./usr/lib64/python3.11/lib-dynload/termios.cpython-311-x86_64-linux-gnu.so` or `./usr/lib64/python3.11/lib-dynload/_codecs_tw.cpython-311-x86_64-linux-gnu.so` so maybe it's removing extended attributes? IDK
- `strip -s usr/lib/* usr/lib64/* usr/bin/*` as recommended by :slackware_admin:building_a_package
- `mkdir install && cd install && wget -desc` to add a `slack-desc` file to the package
- edit the usr/bin/pip3 and other pip files to point to python3 instead of just python, as this package doesn't install a default python
- `cd /tmp/package-python-make-output && /sbin/makepkg -l y -c n /tmp/python3-3.11.4-x86_64-1.txz` to actually make the output Slackware package using all the files in the `/tmp/package-python-make-output` directory