Groups | Search | Server Info | Keyboard shortcuts | Login | Register [http] [https] [nntp] [nntps]


Groups > comp.lang.forth > #32945 > unrolled thread

Patching the MSDOS-booter?

Started byUnknown <dog@gmail.com>
First post2014-08-16 11:56 +0000
Last post2014-08-16 11:56 +0000
Articles 1 — 1 participant

Back to article view | Back to comp.lang.forth


Contents

  Patching the MSDOS-booter? Unknown <dog@gmail.com> - 2014-08-16 11:56 +0000

#32945 — Patching the MSDOS-booter?

FromUnknown <dog@gmail.com>
Date2014-08-16 11:56 +0000
SubjectPatching the MSDOS-booter?
Message-ID<pan.2014.08.16.12.02.15@gmail.com>
This is just pasted from my reply re. jonesForth for rPi:-----

OK, that looks interesting, but to avoid the need to buy & keep
new SDs for each such experiment; eg. TinyCore ...etc.,
I wonder if it's possible to 'fix' the SDs MSDOS booter, so that
by just dd-ing a few bytes [via your card-reader], you could
point the <load and run> to various such systems.

I don't expect the following to work, but just as a naive concept:
= if MSDOS booter jumps/starts the 1st-of-4 partitions which is
  marked-as-bootable [needs only 1 byte to be set], the simplistically
  that seems that you could direct the rPi to run different bare-metal
  aps from the same SD. Of course not without 'reprogramming' it.
OTOH perhaps you could use what I've been doing to mark sound-files
with only on on/off-switch: 
FOR i := 1 TO n
  mark the file i;
  Prompt to cutNowFor iMarked;
  restoreFileToDefaultMarking

This would allow the SD to be programmed by the last-set/run ap.

[toc] | [standalone]


Back to top | Article view | comp.lang.forth


csiph-web