similar to: Ghostcast random freeze.

Displaying 20 results from an estimated 2000 matches similar to: "Ghostcast random freeze."

2018 Feb 01
2
syslinux PXE boot version upgrade, network no longer working
Hardware with issue is a Lenovo T410 (circa 2007?): SysLinux PXE boot (pxelinux.0) version 2009 - PXE boot works, select Ghost from PXE menu, PC-DOS loads, Ghost.exe runs and networking is working for Ghostcast/peer to peer. SysLinux PXE boot (pxelinux.0) version 2014 - PXE boot works, select Ghost from PXE menu, PC-DOS loads, Ghost.exe runs and networking is NOT working for Ghostcast/peer to
2010 Mar 17
1
USB Thumbdrive + dos ghost boot image + drive too small = confusion
I will really hate myself if this has already been solved, i searched the archives but didn't really find anything pertaining to it. I have a 2.88mb dos boot floppy image, with ghost.exe, dos nic drivers, and dos system files. It works fine when burnt to a cd. As for the thumbdrive when trying to configure this hpghost.ima file to run from my syslinux.cfg menu, it works and boots up fine but
2018 Feb 02
2
syslinux PXE boot version upgrade, network no longer working
My ?default? was just a sample to prevent further tl;dr :) Right, by 2014 I meant 6.03. I didn?t notice in the docs this was a known issue. If keeppxe is a bug with 6.03, that?s likely my issue. Do I drop back to 6.02 or X? Which version? Thanks, David Sent from my iPhone > On Feb 1, 2018, at 6:53 PM, Ady Ady via Syslinux <syslinux at zytor.com> wrote: > > >> Hardware
2005 Oct 07
1
tftp pxe and dos
So I have a few questions. I have already made the base part of making a windows TFTPD running with memedisk. So that part works, but what I was wondering, if there is a way to some how add an option to the config file. What I have is something like this: label winstall kernel unattended/memdisk append initrd=unattended/winstall.imz That all works great, However, for each image, I have
2018 Feb 01
0
syslinux PXE boot version upgrade, network no longer working
> Hardware with issue is a Lenovo T410 (circa 2007?): > > SysLinux PXE boot (pxelinux.0) version 2009 - PXE boot works, select > Ghost from PXE menu, PC-DOS loads, Ghost.exe runs and networking is > working for Ghostcast/peer to peer. > > SysLinux PXE boot (pxelinux.0) version 2014 - PXE boot works, select > Ghost from PXE menu, PC-DOS loads, Ghost.exe runs and networking
2010 Jan 11
6
Dell problems with PXELINUX 3.62
Hello. We've been using a very old version of SYS-/PXELINUX, 3.36, going by the proven "if it works, don't break it" philosophy. We us it mostly to load floppy disk images to kick off OS installations. Unfortunately we've recently had some PXE menu problems (USB keyboard stopped working) for a certain Fujitsu PC model, and decided to upgrade to the latest version, i e 3.84.
2016 Nov 03
2
rotl: undocumented LLVM instruction?
Is there any way to get it to delay this optimization where it goes from this: Initial selection DAG: BB#0 'bclr64:entry' SelectionDAG has 14 nodes: t0: ch = EntryToken t2: i64,ch = CopyFromReg t0, Register:i64 %vreg0 t4: i64,ch = CopyFromReg t0, Register:i64 %vreg1 t6: i64 = sub t4, Constant:i64<1> t7: i64 = shl Constant:i64<1>, t6
2007 Jul 19
4
Help Memdisk + Pxelinux hangs
Hello, I am a *nix newbie I am trying to boot a DOS boot disk using PXE (to Ghost on windows images). We have an existing PXE server which successfully serves out PXElinux and Fedora builds based on that but my floppy disk image with memdisk isn't working I have tried a few different floppy images which people have posted as ones that work for them but I doubt the disk is the problem
2016 Nov 03
3
rotl: undocumented LLVM instruction?
Setting the ISD::ROTL to Expand doesn't work? (via SetOperation) You could also do a Custom hook if that's what you're looking for. On Thu, Nov 3, 2016 at 5:12 PM, Phil Tomson <phil.a.tomson at gmail.com> wrote: > ... or perhaps to rephrase: > > In 3.9 it seems to be doing a smaller combine much sooner, whereas in 3.6 > it deferred that till later in the
2009 Sep 29
1
How to parsing data like this in R
Hi, R-users, I met a problem: Items:[Anna 'moi =) akku loppu joskus 4ltä. Kestää kauan nää..'\tAmer, Tuusula (0:20)\t20\t12\t16\t00\t00\t11]/Anne 'Ei jakoa,uus päivä muistio et 4n niin peruin. Hups'\t (0:16)\t0\t12\t18\t00\t00\t11/Elina 'Konsertissa. En tod. vastaa teille'\tEtu-Töölö, Helsinki (2:40)\t24\t12\t18\t00\t00\t11 I want to parsing the above data into the
2016 Nov 03
2
rotl: undocumented LLVM instruction?
One option may be to prevent the formation of ROTL, if possible, and then generating rol by hand. Marking it as "expand" would likely stop the DAG combiner from creating it. Then you could "preprocess" the selection DAG before the instruction selection and do the pattern matching yourself. -Krzysztof On 11/3/2016 4:24 PM, Phil Tomson via llvm-dev wrote: > I could try
2016 Nov 02
3
rotl: undocumented LLVM instruction?
We've recently moved our project from LLVM 3.6 to LLVM 3.9. I noticed one of our code generation tests is breaking in 3.9. The test is: ; RUN: llc < %s -march=xstg | FileCheck %s define i64 @bclr64(i64 %a, i64 %b) nounwind readnone { entry: ; CHECK: bclr r1, r0, r1, 64 %sub = sub i64 %b, 1 %shl = shl i64 1, %sub %xor = xor i64 %shl, -1 %and = and i64 %a, %xor ret i64
2016 Jun 22
2
LLVM Backend Issues
Thanks Anton and Krzysztof! Here is the dump using the -debug flag. At this point I am not making much sense of this, would it be too much to ask if one of you could walk me through one of these lines? One thing that I didn't point out is that I never defined any separate floating point registers, not sure if this will pose any issue? Thanks again for your time! Jeff jeff at
2009 Aug 01
10
PXE + memdisk booting problems
Sorry for makeing a new post, but I already erased my old mails. In the following I describe my Server-Situation (Sorry for my bad english) * I have a eisfair server http://www.eisfair.org with version 1.6.1 (newest) * I have a ISC-DHCPD 3 Server running * I have a TFTP Server running http://www.kernel.org/pub/software/network/tftp/ * I have Samba installed and a DNS Server is running My
2007 Mar 01
2
[LLVMdev] Version 1.9 SSA form question
int %nlz10(uint %param.x) { %.t3 = shr uint %param.x, ubyte 1 ; <uint> [#uses=1] %.t4 = or uint %.t3, %param.x ; <uint> [#uses=2] %.t7 = shr uint %.t4, ubyte 2 ; <uint> [#uses=1] %.t8 = or uint %.t7, %.t4 ; <uint> [#uses=2] %.t11 = shr uint %.t8, ubyte 4 ; <uint> [#uses=1]
2007 Sep 15
2
keeppxe+memdisk+FreeDOS example?
Hi, I'm trying to get the above working, without success so far: UNDIS.DOS refuses to load with an invalid NDIS stack message (from memory). keeppxe has some effect: it reduces the available conventional memory by 140 kbytes or so... still, the packet driver doesn't seem to find the interface. Does anybody have a working setup I could look at? -- Thanks, Feri.
2008 Jan 24
3
store variable as tab-del. txt-file
Hallo, how can I store a variable as a tab-delimited txt-file? I crated a variable with the following commands: > fit12<-lmFit(qrg[,1:2]) > t12<-toptable(fit12,adjust="fdr",number=25,genelist=qrg$genes[,1]) > t12 ID logFC t P.Value adj.P.Val B 522 PLAU_OP -6.836144 -8.420414 5.589416e-05 0.01212520 2.054965 1555 CD44_WIZ -6.569622
2008 Feb 11
3
Difference between P.Value and adj.P.Value
Hallo, > fit12<-lmFit(qrg[,1:2]) > t12<-toptable(fit12,adjust="fdr",number=25,genelist=qrg$genes[,1]) > t12 ID logFC t P.Value adj.P.Val B 522 PLAU_OP -6.836144 -8.420414 5.589416e-05 0.01212520 2.054965 1555 CD44_WIZ -6.569622 -8.227938 6.510169e-05 0.01212520 1.944046 Can anyone tell me what the difference is between P.Value
2009 Apr 14
5
"keeppxe" broken in 3.74 - short-cycle 3.75
It appears that the 3.74 completely broke the "keeppxe" directive -- not due to the command-line parser, but due to mishandling of the flag later. I consider this to be severe enough to do a short-cycle 3.75. As a result, I would like help with: a) are there any other bugs that snuck through? b) once I have a 3.75-pre1, I would really appreciate help testing it. The goal is to have
2006 Jan 03
0
Isolinux.cfg issues on certain BIOSes
Howdy to all, We've been using isolinux quite successfully for quite some time now, and I have come across a couple of laptops where isolinux balks at my config file.. Upon booting on this systems, the image background appears corrupted, and at the boot prompt, the following happens automatically. Unknown keyword in config file. Could not find kernel image: 1 boot: Any label input here