Displaying 4 results from an estimated 4 matches for "e700".
Did you mean:
0700
2009 Mar 23
1
Memdisk + Freedos problem
...===============================
FreeDOS HIMEM64 3.26 [Aug 25 2006] (c) 1995, Till Gerken 2001-2005 tom ehlert
HIMEM - Fast A20 method used
UMBPCI c't 11/95 - Siering/Sch?pers/Stiller
V3.77 - support for new chipsets, Inter PPro, AMD K7 - Uwe Sieler 08/2008
AMD K8 CPU found
Using CF00-E2FF
Using E700-E7FF
Program installed
LowDMA (haftman# software 11/01): installed
Kernel: allocated 34 Diskbuffers = 18088 Bytes in HMA
Invalid Opcode at 5281 FFFF 0286 E0A0 0000 0000 0000 0000 E0A0 0000 017C 0000 0D86
==========================================================
Then it halts.
2 Boot UMBPCI (op...
2015 Sep 26
1
Tinc clients behind a NAT, tunnels get unstable
Hi,
Am Samstag, den 26.09.2015, 15:45 +0200 schrieb Marcus Schopen:
> Hi,
>
> Am Samstag, den 26.09.2015, 12:20 +0200 schrieb Marcus Schopen:
> > Last Problem seems to be the local UFW Firewall on the clients whichs
> > seems to block the Broadcast for LocalDiscovery = yes. Need to check the
> > logs here.
>
> Puzzeling around with UFW firewall. What ports need
2013 Jan 14
0
[LLVMdev] Obsolete PTX is NOT completely removed in 3.2 release
...: Good signature from "Pawel Wodnicki (elektrknight) <root at 32bitmicro.com>"
gpg: WARNING: This key is not certified with a trusted signature!
gpg: There is no indication that the signature belongs to the owner.
Primary key fingerprint: 4D8F 3DD4 7CBD 5212 7155 AC65 09C4 E700 7CB2 EFFB
gpg: binary signature, digest algorithm SHA1
As for downstreams being involved in the release process, they are. There
is a implicit step that you should write down in your formal processes.
Do NOT change a released tarball for any reason.
We have re-released tarballs over my and...
2013 Jan 17
0
[LLVMdev] Obsolete PTX is NOT completely removed in 3.2 release
...e from "Pawel Wodnicki (elektrknight) <root at 32bitmicro.com>"
> gpg: WARNING: This key is not certified with a trusted signature!
> gpg: There is no indication that the signature belongs to the owner.
> Primary key fingerprint: 4D8F 3DD4 7CBD 5212 7155 AC65 09C4 E700 7CB2 EFFB
> gpg: binary signature, digest algorithm SHA1
>
> As for downstreams being involved in the release process, they are. There
> is a implicit step that you should write down in your formal processes.
>
> Do NOT change a released tarball for any reason.
>
> W...