| Newsgroups |
gmane.comp.emulators.hercules390.general |
| Message-ID |
<[email protected]> |
My loader (PLOAD) is already doing this.
It searches the VTOC for PDOS.SYS and
loads it, processing the relocations too.
The problem is that my loader is written
in C so there is the baggage of the C
runtime library, so it is bigger than one
track.
BFN. Paul.
---In [email protected], <joemonk64@...> wrote :
Seems like MVS has the better approach here.
MVS' IPL is simply a small piece of code that reads the VTOC on the IPL disk and then searches the Format 1 DSCBs looking for sys1.nucleus.
You could do the same thing... read the VTOC and find your files ... then load/execute.
Joe
On Tue, Mar 19, 2019 at 12:48 PM kerravon86@... mailto:kerravon86@... [hercules-390] <[email protected] mailto:[email protected]> wrote:
It wouldn't. It would rely on the first block of
the IPL program to load the remaining
records. PLOAD is already doing this.
Similar to how the boot sector of
an MSDOS disk only loads the first 3
sectors of IO.SYS.
BFN. Paul.
---In [email protected] mailto:[email protected], <joemonk64@...> wrote :
"My proposal is that the IPL
program can be larger than 1 track."
And how does the IPL CCW know to read more than 1 track? You've disclaimed the use of TIC (transfer in channel)...
Joe
On Tue, Mar 19, 2019 at 5:41 AM kerravon86@... mailto:kerravon86@ mailto:kerravon86@... [hercules-390] <[email protected] mailto:[email protected] mailto:[email protected] mailto:[email protected]> wrote:
Hi Mark.
My proposal is not to have record/track
overflow. My proposal is that the IPL
program can be larger than 1 track.
In my case the IPL program is 113k.
Even an entire track is not enough.
dasdload just needs to support putting
the IPL program on multiple tracks.
BFN. Paul.
---In [email protected] mailto:[email protected] mailto:[email protected] mailto:[email protected], <mark_s_waterbury@...> wrote :
Paul,
Unlike most S/370 era DASD, 3330 up through 3380 and 3390, the 9340 subsystems do not support "record overflow" (sometimes called "track overflow"). So, why would you propose to modify Hercules-390 to implement such a non-standard feature?
Mark S. Waterbury
---In [email protected] mailto:[email protected] mailto:[email protected] mailto:[email protected], <kerravon86@...> wrote :
---In [email protected] mailto:[email protected] mailto:[email protected] mailto:[email protected] mailto:[email protected] mailto:[email protected] mailto:[email protected] mailto:[email protected], <ivan@...> wrote :
>> So? All I did was waste less than 56,664
>> bytes by moving the program to be IPLed
>> from 0/0/4 to 0/1/1.
>>
>> And I'm even discussing software changes
>> so that that "issue" can be reversed by
>> having a Hercules change to allow the IPL
>> program to start on 0/0/4 but extend onto
>> the next head and beyond.
> Why are we discussing your personnal pet
> peeve project issues on this
> mailing list already ?
> What does this have to do with hercules ?
Perhaps you missed the phrase "Hercules
change" in the paragraph above, discussing
how Hercules can be used to build an
IPLable DASD. I don't see how it can be
any more on-topic. Using Hercules to run
S/390 software. ie hercules-390.
Also note that the standalone code being
discussed is INDEPENDENT of PDOS.
It can be used to write any standalone
program to run under Hercules. I even
asked Dave M if he could use the code
to do his bare metal 3270 coding.
BFN. Paul.