search for: 80486

What's the deal with Windows setup? I tried running setup to see if I could install Windows 98 in Wine to set up the necessary dlls and such, and it complains "Windows 98 requires a computer with an 80486 processor or higher." I'm running a P-II. Does Wine report back something other than the actual processor, or is there something else going on? Thanks, Dave -- ---------------------------------------------------------------------- Dave Walton...

( I don't know if it's allowed to ask such question, if not, please remind me. ) I know Intel implemented several static branch prediction mechanisms these years: * 80486 age: Always-not-take * Pentium4 age: Backwards Taken/Forwards Not-Taken * PM, Core2: Didn't use static prediction, randomly depending on what happens to be in corresponding BTB entry , according to agner's optimization guide ¹. * Newer CPUs like Ivy Bridge, Haswell have become increa...

...,19200n81 ramdisk_size=16384 root=/dev/ram0 init=/linuxrc rw initrd=initrd-net4521 IPAPPEND 1 -------------- These are the boot messages I get on my minicom. =========== comBIOS ver. 1.15 20021013 Copyright (C) 2000-2002 Soekris Engineering. net45xx 0064 Mbyte Memory CPU 80486 133 Mhz PXE-M00: BootManage UNDI, PXE-2.0 (build 082) ..ot Vend Dvv ClassRev Cmd Stat CL LT HT Base1 Base2 Int 6HLinux version 2.6.6-net4521 (root at localhost.localdomain) (gcc version 3.2.2 24BIOS-provided physical RAM map:2280 00 00 00 00000000 00000000 00 BIOS-e801: 00000000000000...

Building on Mac OS X doesn't work. It fails with this error: configure: error: No 16 bit type found on this platform! I've posted the config.log here: https://gist.github.com/1878663 I think something is going wrong with how the configure script is detecting the platform. Thanks, aaron -------------- next part -------------- An HTML attachment was scrubbed... URL:

Hi all: I hope someone can help me with this "little" problem... I''m using a linux script to sub-divide my bandwidth (64kbit) into: 40kbit for VOIP, and the remaining 24kbit for http. So, the commands I''m using are: ============================================ #!/bin/bash # This script shapes "downloading" stuff # Initial qdisc tc qdisc add dev eth1

...+(* Convert output from 'file' command on ELF files to the canonical + * architecture string. Caller must free the result. + *) +and canonical_elf_arch bits endianness elf_arch = + let substr s = String.find elf_arch s >= 0 in + if substr "Intel 80386" || substr "Intel 80486" then + "i386" + else if substr "x86-64" || substr "AMD x86-64" then + "x86_64" + else if substr "SPARC32" then + "sparc" + else if substr "SPARC V9" then + "sparc64" + else if substr "IA-64&qu...

Help please- I am running 3.3.1 on Centos using a 10GB network. I get reasonable write speeds, although I think they could be faster. But my read speeds are REALLY slow. Executive summary: On gluster client- Writes average about 700-800MB/s Reads average about 70-80MB/s On server- Writes average about 1-1.5GB/s Reads average about 2-3GB/s Any thoughts? Here are some additional details:

Version 1 was here: https://www.redhat.com/archives/libguestfs/2017-June/msg00003.html This patch series reimplements a few more APIs in OCaml, including some very important core APIs like ?list_filesystems? and ?mount?. All the tests pass after this. The selection of APIs that I have moved may look a little random, but in fact they are all APIs consumed by the inspection code (and some more

v2 was here: https://www.redhat.com/archives/libguestfs/2017-June/msg00008.html This series gets as far as a working (and faster) reimplementation of ‘guestfs_list_filesystems’. I also have another patch series on top of this one which reimplements the inspection APIs inside the daemon, but that needs a bit more work still, since inspection turns out to be a very large piece of code. Rich.

I think this fixes everything mentioned: - Added the Optgroups module as suggested. - Remove command temporary files. - Replace command ~flags with ?fold_stdout_on_stderr. - Nest _with_mounted function. - Rebase & retest. Rich.

v1 was posted here: https://www.redhat.com/archives/libguestfs/2017-July/msg00098.html This series now depends on two small patches which I posted separately: https://www.redhat.com/archives/libguestfs/2017-July/msg00207.html https://www.redhat.com/archives/libguestfs/2017-July/msg00209.html v1 -> v2: - Previously changes to generator/daemon.ml were made incrementally through the patch

Previously posted as part of the mega utilities/inspection series here: https://www.redhat.com/archives/libguestfs/2017-June/msg00232.html What I've done is to extract just the parts related to rewriting daemon APIs in OCaml, rebase them on top of the current master, fix a few things, and recompile and test everything. Rich.

This is a combination of: https://www.redhat.com/archives/libguestfs/2017-June/msg00046.html [PATCH 00/12] Refactor utility functions. plus: https://www.redhat.com/archives/libguestfs/2017-June/msg00023.html [PATCH v3 00/19] Allow APIs to be implemented in OCaml. with the second patches rebased on top of the utility refactoring, and some other adjustments and extensions. This passes

v6 was posted here: https://www.redhat.com/archives/libguestfs/2017-June/msg00103.html and this requires the utilities refactoring posted here: https://www.redhat.com/archives/libguestfs/2017-June/msg00169.html Inspection is now complete[*], although not very well tested. I'm intending to compare the output of many guests using old & new virt-inspector to see if I can find any

...} + } + } + return undef unless $found; } return $path; @@ -376,27 +376,27 @@ sub _elf_arch_to_canonical local $_ = shift; if ($_ eq "Intel 80386") { - return "i386"; + return "i386"; } elsif ($_ eq "Intel 80486") { - return "i486"; # probably not in the wild + return "i486"; # probably not in the wild } elsif ($_ eq "x86-64") { - return "x86_64"; + return "x86_64"; } elsif ($_ eq "AMD x86-64") { - return "x86_64&...

v5: https://www.redhat.com/archives/libguestfs/2017-June/msg00065.html Since v5, this now implements inspection almost completely for Linux and Windows guests. Rich.

v7 was: https://www.redhat.com/archives/libguestfs/2017-June/msg00169.html https://www.redhat.com/archives/libguestfs/2017-June/msg00184.html I believe this addresses all comments received so far. Also it now passes a test where I compared about 100 disk images processed with old and new virt-inspector binaries. The output is identical in all cases except one which is caused by a bug in blkid