similar to: Any workaround for ThinkPad memdisk?

> Rudy Moore wrote: > > Hi, > > > > I saw the Nov. 2006 message on Memdisk having a problem with ThinkPads. I > also > > saw the comment in the memdisk code enabling and disabling A20. > > > > I've got a ThinkPad x61t that memdisk is not loading disk images on. The > > symptom is that it gets as far as saying "Loading boot sector... >

Hi Peter, Here are the details of a problematic ThinkPad model (an R50e): BIOS version: 2.06 (1WET86WW) BIOS date (YYYY-MM-DD): 2005-11-15 Embedded controller version: 1.04 System-unit serial number: 1834-S5 GL3-BRGZL System board serial number: 1ZB6L5AC1E3 CPU Type: Intel Celeron M CPU Speed: 1.40 GHz Installed memory: 512 MB Booting FreeDOS via current memdisk

(FreeDOS developers, I apologize for the redundant parts of this message. But I want to bring the SYSLINUX folks into the discussion, and the SourceForge mailing list archives are broken.) Background: I have a little Sourceforge project (http://unattended.sourceforge.net/) for which I use SYSLINUX to provide CD-ROM and PXE boot support for my boot disk. And it works great with MS-DOS. However,

I and some other people have problems with running the freedos image included in Ultimate Boot CD (UBCD), when using memdisk for floppy emulation. Memdisk starts booting the image and freedos shows the following menu: 0 Boot Clean 1 Boot UMBPCI (silent) 2 Boot UMBPCI (optimal) 3 Boot UMBPCI (semi-defensive) 4 Boot EMM386 (optimal) 5 Boot EMM386 (semi-defensive) 6 Boot no UMB (defensive) 7 Boot

Hi, I'm doing a small hobby project writing some tools to put DOS boot images and Linux rescue images on a USB stick. For this I have partitioned my USB stick in 2 partitions, one 192MB partition with a VFAT filesystem (for the normal use) and a second partition with an ext3 filesystem. My aim was to provide a graphical menu (grub) to access the different images using memdisk. Since

I found that if I do not have a local floppy installed and enabled on my client, I will get the error 'Non-system disk' when I try to boot DOS floppy images. NT or Syslinux floppy images boot fine. If I enable the floppy in the BIOS, then it boots the DOS floppies just fine. Is this normal? Is there a workaround? There are MS-DOS images, so perhaps this is an MS-DOS limitation. --

Dear Syslinux bootloader list, I'm running into a few issues concerning Syslinux modules here, hoping you can answer one or more of the following questions: * Where's "ifmemdsk.c32" ? 4.05, 4.06pre1 and latest 4.10pre seem to lack it. Only the "ifmemdsk.c" file, which is likely sourcecode. Not seeing any "ifmemdsk.cbt" legacy comboot module. * Do COM32

Hello, I hpe you can help. I have created a botable thumbdrive that allows me to update different bios's using the memdisk module. I have no problems loading the img or ima files on any equiptment other than IBM. I have tried on T43, T60, and T61, no luck. works fine on hp dell and all others tried. Every time after it loads the image it hangs after the message "Loading boot sector...

Hello everybody! Since the update from 6.2-STABLE to 7.0 I'm encountering problems with the temperature of my Thinkpad X60s. Under heavy load, e.g., make builworld or compile gcc or... I get the following output in /var/log/messages: Dec 29 01:53:13 delta1 root: WARNING: system temperature too high, shutting down soon! Dec 29 01:53:13 delta1 syslogd: /dev/:0: No such file or directory Dec 29

I have a list of categories, when I delete one of them, I want that item to fade and then get removed. So I do the following: 1. home_controller: def delete @category = Category.find_by_name(params[:name]) @element_id = @category.name Category.delete_all(["name = ?", @category.name]) end 2. delete.rjs: if @element_id page.visual_effect :fade, @element_id

>myDF = data.frame(id=c("A10","A20"),d1=c(.3,.3),d2=c(.4,.4),d3=c(-.2,.5),d4=c(-.3,.6),d5=c(.5,-.2),d6=c(.6,-.4),d7=c(-.9,-.5),d8=c(-.8,-.6)) >doit=function(x)c(x[1],sum_LK_positive=sum(x[-1][x[-1]>0]),sum_LK_negative=sum(x[-1][x[-1]<0])) > myDF id d1 d2 d3 d4 d5 d6 d7 d8 1 A10 0.3 0.4 -0.2 -0.3 0.5 0.6 -0.9 -0.8 2 A20 0.3 0.4 0.5 0.6 -0.2

Hi Some time ago I wrote this mailing list about some extra time that it takes for my system to boot and I don't know where it came from.I'm using a custom BIOS which loads at 1 second and now I've found out that it takes for the bootloader and OS an extra 1 second to load when keyboard is disconnected.I got from the BIOS engineer the following explanation and steps to take: In

Hello, I seemed to have encountered a problem with memdisk that I have seen before when I was playing around with USB device booting at one time. Here's the scenario: Take fx a image of a PC DOS bootable diskette. Boot the image via memdisk. This should boot fine if you use the built-in motherboard ide controllers (ide0,ide1). Now install a PCI IDE controller and put one IDE disk on the

I was working with the rmetrics portfolioBacktesting function and dug into the code to try to find why my formula with 113 items, i.e. A1 thru A113, was being truncated and I only get 85 items, not 113. Is it due to a string length limitation in R or is it a bug in the strsplit or gsub functions, or in my string? I'd very much appreciate any suggestions ============Input script:

The majority of this series went in a while back, what remains is just the basic platform support and the UART blacklisting. The series has also grown a constcorrectness fix for the other existing platforms too. Still no SATA support from upstream sadly. Bamvor has written some generic docs at http://wiki.xenproject.org/wiki/Xen_ARMv7_with_Virtualization_Extensions/Allwinner Thanks, Ian.

Hi There: I was wondering if there is a way to read FORTRAN list data (similar to IDL's readf function). I often use FORTRAN for most of my number crunching, and use something like IDL to visualize and perform statistical analysis on that data. Since the each file is rather large (>100 Mb), formatting the output into columns or tables is impractical, hence the "list"

Hi there, I'm using an embedded device sold by a german company called SSV. Further Information about the device can be found on the following URL. http://www.ssv-embedded.de/ssv/pc104/p170.htm The IDE Interface is a very basic one. Starting with syslinux 1.51 the system stopped booting correctly (1.67 does not work as well). With syslinux Version up to 1.50 erything works fine. The boot

Hi Ian, I try compile the bootwrapper for cubieboard2 like this: joshzhao@joshzhao-ThinkCentre-M58p:~/project/Xen/A20/boot-wrapper$ make cubieboard2_defconfig CROSS_COMPILE=arm-linux-gnueabihf- # # configuration written to .config # joshzhao@joshzhao-ThinkCentre-M58p:~/project/Xen/A20/boot-wrapper$ make CROSS_COMPILE=arm-linux-gnueabihf- make -C scripts/kconfig -f Makefile.bootwrapper

See http://www.gossamer-threads.com/lists/xen/devel/297170 for some information on how to get this going. I''ve rebased and addressed the review comments. With this rebase I''ve picked up some patches from Julien which were required to do things properly, so the gic v7 and device blacklisting patches have been changed to use the proper mechanisms. Previously I was able to boot

Shantanu, let's continue here. You first noticed this on a Dell OptiPlex 755. I think it covers all Dell OptiPlex/Latitude/Precision models that are PCIe based with Intel LoM (LAN on motherboard) utilizing the BIOS PXE OROM, based on the similarity of these systems. The symptoms are that PXELINUX requests pxelinux.cfg/<UUID> by TFTP (but it might not strictly be a TFTP issue) when not