From: Tim Small <tim@buttersideup.com>
To: Mark Knecht <markknecht@gmail.com>
Cc: Phillip Susi <psusi@cfl.rr.com>, Bill Davidsen <davidsen@tmr.com>,
st0ff@npl.de, linux-raid@vger.kernel.org
Subject: wdidle3
Date: Thu, 22 Apr 2010 12:40:37 +0100 [thread overview]
Message-ID: <4BD035B5.2010203@buttersideup.com> (raw)
In-Reply-To: <m2x5bdc1c8b1004211201ob1ea0c67k67b03eb4627a1375@mail.gmail.com>
Mark Knecht wrote:
>> [wdidle3.exe]...
> Yeah, that's been reported here before, but how does someone run this
> Windows program on a remote machine that boots only Linux? Even if it
> was a DOS executable the machine has no floppy.
It is a DOS executable. As previously mentioned, you can use:
USB floppy emulation (if the BIOS supports it)
USB HD emulation
Booting from an HD partition (e.g. temporarily break RAID for one of the
swap partitons, and install DOS in that partition).
syslinux + memdisk + image file
pxelinux + memdisk + image file
I use the latter for using DOS bios upgrades etc. remotely using IPMI+SoL.
If anyone want to try and reverse-engineer wdidle3, it appears to have
been compiled with Watcom (now open source), and a free DOS extender and
then packed (again using an open tool). You can run it under the Watcom
disassembler / debugger (which is packaged with FreeDOS).
With all this open source software rattling around Western Digital, it'd
be nice if they just did a bloody Linux version (or at least documented
the vendor-specific commands which they use).
Tim.
next prev parent reply other threads:[~2010-04-22 11:40 UTC|newest]
Thread overview: 52+ messages / expand[flat|nested] mbox.gz Atom feed top
2010-03-25 16:20 Use of WD20EARS with MDADM Andrew Dunn
2010-03-25 17:01 ` Asdo
2010-03-25 17:58 ` Mark Knecht
2010-03-25 20:23 ` John Robinson
2010-03-26 10:45 ` Asdo
2010-03-25 17:10 ` David Lethe
2010-03-25 17:45 ` Asdo
2010-03-28 16:19 ` Stefan *St0fF* Huebner
2010-03-29 16:59 ` WD20EARS data Stefan /*St0fF*/ Hübner
2010-03-29 17:13 ` Stefan /*St0fF*/ Hübner
2010-04-14 19:53 ` Use of WD20EARS with MDADM Bill Davidsen
2010-04-19 14:17 ` Phillip Susi
2010-04-21 13:20 ` Bill Davidsen
2010-04-21 13:45 ` Tim Small
2010-04-21 14:32 ` Mikael Abrahamsson
2010-04-21 21:58 ` Berkey B Walker
2010-05-02 22:33 ` Bill Davidsen
2010-05-03 0:08 ` Berkey B Walker
2010-04-21 15:14 ` Phillip Susi
2010-04-21 16:42 ` Bill Davidsen
2010-04-21 17:36 ` Mark Knecht
2010-04-21 18:40 ` Tim Small
2010-04-21 19:01 ` Mark Knecht
2010-04-21 19:31 ` Clinton Lee Taylor
2010-04-22 0:51 ` Steven Haigh
2010-04-21 19:33 ` Phillip Susi
2010-04-21 20:36 ` Mark Knecht
2010-05-12 13:06 ` Tim Small
2010-04-22 11:40 ` Tim Small [this message]
2010-04-22 16:13 ` Khelben Blackstaff
2010-04-22 18:16 ` Simon Matthews
2010-04-22 19:44 ` Phillip Susi
2010-04-22 23:23 ` Mark Knecht
2010-04-23 0:03 ` Richard Scobie
2010-04-23 1:29 ` Mark Knecht
2010-04-23 3:49 ` Phillip Susi
2010-04-23 3:44 ` Phillip Susi
2010-04-21 15:52 ` Simon Matthews
2010-04-21 19:24 ` Richard Scobie
2010-03-26 20:27 ` Peter Kieser
2010-03-26 20:59 ` Mark Knecht
2010-03-26 21:01 ` Peter Kieser
2010-03-26 21:06 ` Mark Knecht
2010-03-26 21:16 ` Mark Knecht
2010-03-26 21:19 ` Richard Scobie
2010-03-26 22:38 ` Mark Knecht
2010-03-26 22:47 ` Peter Kieser
2010-03-26 22:50 ` Matt Garman
2010-03-26 22:51 ` Peter Kieser
2010-03-26 23:01 ` David Rees
2010-03-27 23:31 ` Mark Knecht
2010-03-26 21:45 ` Matt Garman
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=4BD035B5.2010203@buttersideup.com \
--to=tim@buttersideup.com \
--cc=davidsen@tmr.com \
--cc=linux-raid@vger.kernel.org \
--cc=markknecht@gmail.com \
--cc=psusi@cfl.rr.com \
--cc=st0ff@npl.de \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.