search for: gx280

...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. All seemed well until we got reports about problems with Dell OptiPlex GX280. I've done some testing and everything works well until version 3.62. After the floppy image has been loaded and it starts executing DOS 7.0 (Win98), there are several error messages about DOS memory. GDISK also can't run, complaining about DOS memory. This problem can be reproduced with...

...perhaps a leftover of PXELINUX. Even though the second run of XMSDSK succeeds, the cabinet extraction does not fully succeed. I decided to rule out PXELINUX, so instead I put GRUB4DOS 0.4.4 on the local HDD. I booted to the HDD and ran GRUB4DOS. From its CLI, I did: kernel /memdisk initrd /dellgx280.imz and encountered the same failures as the PXELINUX case. The "raw," "bigraw," "int," and "safeint" (default) modes all produce the same failure. Then I tested using GRUB4DOS' non-memory drive mapping technique, which also failed. To do this, I used...

...= f0005c6f int15 = f000f859 int1e = f000efc7 new: int13 = 9f00000a int15 = 9f0003ba int1e = f000efc7 Loading boot sector... press any key to boot... No 'lost drive' message was reported and the internal hard drive is now visible to the booted environment. I also tried (only on the OptiPlex GX280, at this time) this debug version with my Ghost client image from previous trials, and it works. Yay. So does this mean the genius team has fixed the issue? I can perform further testing, but the latest changes look promising indeed. Much thanks. Regards. ----- Original Message ----- From: "...

...k. Well, the same error message and results occur when PXE-booting and MEMDISK-loading a FreeDOS hard disk image. MEMDISK 3.83 (and previous) versions work properly, but any version beyond the 3.83 (including the 4.x series) do not work so properly. I thought this occurrence was unique to OptiPlex GX280 and GX620 systems, but a number of Latitude notebooks have joined the party. Below is the rundown of systems and MEMDISK results. initrd image: c.img (A FreeDOS image) extracted from the following archive: http://bochs.sourceforge.net/guestos/freedos-img.tar.gz ---------------------------------...

I've got echo problems. *** I'm looking for paid support. *** I'll accept free support, but don't mind paying if someone really knows what they are doing. I've read the wiki, etc. Played with the settings in zapata.conf Using V400P PSTN->_T1->_ASTERISK->_BROADVOICE->_PSTN ECHO ON CALLED PHONE PSTN->_T1->_ASTERISK->_T1->_PSTN NO ECHO

A kind request for help please. MEMDISK is causing an issue with the Dell OptiPlex GX280 and GX620 platforms. Booting a PC-DOS/Ghost, disk image is successful (and proper) when using version 3.83. See results below: MEMDISK 3.83: Ramdisk at 0x07eeaa00, length 0x007bc000 command line: initrd=images/ghostclient/280_620/osbootc.img BOOT_IMAGE=memdisk MEMDISK: Image seems to have fractio...

Hello, =20 Something wrong happens when I use the seq (function). Here it is an exampl= e from my R console, I have the R version 2.7.2 (2008-08-25) running on Mic= rosoft windows XP Version 2002 Service Pack 3, and my machine is a Dell Opt= ilex GX280 with a processor Intel Pentium 4 CPU 2.80GHhz, 0.99 GB RAM: =20 =20 >r=3Dseq(0.150,0.180,0.001) =20 > r[16] =20 [1] 0.165 =20 > class(r[16]) =20 [1] "numeric" =20 > for (i in (150:180)/1000) =20 + show(which(r=3D=3Di)) =20 [1] 1 [1] 2 [1] 3 [1] 4 [1] 5 [...

...even tried 3.35 out of desperation. Even formatting and setting everything up from scratch as I have done in the past doesn't cure the problem (I use the win32 executable syslinux -mad boot f:). The problems are occuring on the exact same PC I was using before getting the problems (a Dell GX280 A06), and I tried some other PCs too just in case. Any suggestions? I'm lost without this - didn't realise how much I used it! Thanks Chris ***Disclaimer**** This e-mail and any attachments are for the intended addressee(s) only and may contain confidential and/or privileged material...

...ugh the archives and did not see any reference to this problem. I have an MS-DOS boot floppy image that I am trying to load using MEMDISK. The disk is simply a boot floppy made using XPSP2. I have tried it on 4 different machines, all Dells. PowerEdge 2650 Server, Latitude D610 Notebook, Optiplex GX280 Desktop and Optiplex GX520 Desktop. The boot is successful on the server and laptop but somewhat unsuccessful on the Optiplexes. The optiplexes have SATA drives but I don't know if that makes a difference. I say somewhat unsuccessful because through some trial-and-error I have discovered that...

Hello, I''m trying to build XenLinux 2.4.30 on debian. I get the following error for make linux24 make[2]: *** No rule to make target `skbuff.c'',needed by `/usr/src/xen-2.0/linux-2.4.30-xen0/include/linux/modules/skbuff.ver''. Stop. Could somebody help me resolve this error. Or if this is some problem with the system configuration that I''m using, could

Just gave 3.0 a spin. Had been running 2.0.7 for the past 3 months or so without problems (aside from intermittent failure during live migration). Anyway, 3.0 seems to have an issue with my machine. It starts up the 4 domains that I''ve got defined (was running 6 user domains with 2.0.7, but two of those were running 2.4 kernels which I can''t seem to build with Xen 3.0 yet, and