![]() | |
#31
| |||
| |||
|
|
Last night I was prompted by a link to read one of Henry Eggers' CDP posts which makes me curious; how many programmers are still around who at one time worked on *Native* Pick and its variants like ADDS, Microdata, Ultimate and such? Henry Keultjes hbkeultjesatarthlinkdotnet Microdyne Company Mansfield Ohio USA |
#32
| |||
| |||
|
|
My first Pick box was an ADDS Mentor in Tampa Florida circa 1982. On Sep 4, 5:28*am, hbkeultjes <hbkeult... (AT) gmail (DOT) com> wrote: Last night I was prompted by a link to read one of Henry Eggers' CDP posts which makes me curious; how many programmers are still around who at one time worked on *Native* Pick and its variants like ADDS, Microdata, Ultimate and such? Henry Keultjes hbkeultjesatarthlinkdotnet Microdyne Company Mansfield Ohio USA |
#33
| |||
| |||
|
|
My objective is the have an ARM-64 based box that runs an Exo-kernel |
#34
| |||
| |||
|
|
On Sep 5, 8:27*pm, hbkeultjes <hbkeult... (AT) gmail (DOT) com> wrote: On Sep 5, 4:02*pm, Tony Gravagno <nos... (AT) nospam (DOT) invalid> wrote: hbkeultjes wrote: sdavmor wrote: I think most of them have picked up their toys and long since gone home (from cdp). Why use something, like Pick Virtual Assembler when those who can use those tools are a tiny tiny tiny fraction of those who know how to use Open Source Assembler and high-level languages to write systems code? Because the other languages don't work within the Pick environment or on Pick data like PVA. PVA is used exclusively inside the DBMS, and to my understanding, D3 is the only platform left where third-party developers can use PVA. This is about building a new system, not a virtual system, and thus it would use an assembler for the specific processor which in this case would be ARM-64. Once again I don't even understand what this thread is about. *There seems to be confusion between "Native" Pick and PVA: - Native Pick is any system that doesn't run over a native OS because it _is_ the native OS. You are exactly right so Native Henry would-be-the-OS-and-the-Database and whatever else, just like Native Pick. This includes both the old software and > firmware machines, and AP/ Native and AP/Pro. - Native Pick became obsolete when Pick was ported over an OS layer, namely Unix and then Windows. Obsolete is, of course, relative because our Native Pick works just as good as it ever did, but the reason I am looking for something better is because in character mode I cannot do all the things I want to do yet I want to have a single integrated system just like Native Pick is. - Native Pick used PVA inside the DBMS, but the current D3 uses virtually the same PVA. *Usage or non-usage of PVA have nothing to do with whether the platform is native or not because it's a step removed from the platform layer. Whereas I don't care about that virtual layer, don't want it, don't need it because I want to run on only one processor, an ARM-64 when that becomes available. - The language used under the MV environment, to integrate the DBMS with the OS (the platform layer), is OS-specific assembler and/or C/C++, depending on the platform, but this assembler is completely unrelated to PVA. In my case the assembler will be ARM-64 specific and not Linux specific. *That assembler will build the "Henry" system code on top of which application code runs which application code will be written in just one language, *a type of Basic that will have new additions to do whatever needs to be done. *Remember, any application can do only what can be reflective of the instruction set so if you need to do something that a certain Basic cannot do, the typical answer has been to find a different language can do it and thus you have both a solution and a problem. *I prefer the solution without the problem. Pick did pretty amazing things with DataBasic. *I believe that the "Henry System" can do pretty amazing thins with "Henry Basic". By definition, PVA is "virtual" and not tied to the machine itself. This is why PVA can run over a variety of hardware/software platforms.. It's just like emulator programs where you can play Atari or video arcade games on your PC, because the assembler for those games (the ROM) is parsed and processed by a lower tier that actually executes the instructions. Yes, indeed. *The only way to get work done on a processor is to use the instruction set, with machine language or with a processor specific compiler. PVA is completely unique to the Pick environment. *It's based on registers, bits, and bytes just like any BAL but all of the data is resident in frames within the environment, not in CPU/memory registers. What am I missing? *Is there a hard and fast reason that other systems could not work like that without any PVA, * Ultimately the chip has to this so it is just a matter of instructing it to do it. * That nobody else has ever done that does not mean that it is impossible. *If the public domain concept of Pick can be implemented using a PVA it can be implemented without the PVA. and without a firmware board but in a SoC ARM implementation, programmable logic might be more efficient for such an implementation than software. **Other languages cannot access the in-frame data which is operated upon by PVA (well, I could do it if someone put a gun to my head) and PVA cannot be replaced or augmented with another language. I hope that I explained this well enough now to convey that PVA does not matter. *My first objectives of this threat was to get people buy into the idea of a better Pick than Native Pick that was just as good (can I say dear to us) as Native Pick. The other objective was to convey the futility of trying to build on the old foundation because there are not enough people left that know how to lay those old "bricks". *My objective is to have the same system with increased functionality and use Open Source "bricks" that literally thousands of people all across the globe know how to lay. *The third objective is to inspire those who know Pick, at whatever level, to suggest pieces that might work to do this but all I get is suggestions of doing it the way I don't want to do it. *C'est la Vie! The notion of replacing PVA with another assembler is pure fantasy - and once again without some definition of a usage case for doing so You might be right but it does not matter because no type of PVA is in my plans. . There are only a few products left in the MV market that are completely reliant on PVA, and so far it has not been cost-justified for them to transition away from it. Until I would see the numbers I could not comment on that. If you want an environment where PVA does not exist, consider QM or one of the other platforms not descended from R83. Correct me if I am wrong but I believe that QM is still strictly an ASCII environment that runs on top of Linux (or whatever) and thus is not a single integrated platform that supports a modern browser that I am looking for. Henry Keultjes Mansfield Ohio USA T- Hide quoted text - - Show quoted text - Long post, long answers. But if the bottom line is using a browser there is no issue, if the bottom line is using a mouse then use the Accuterm UI. *But if the bottom line is running a business then I quote Dick "The mouse is not a business tool." Bobj |
#35
| |||
| |||
|
|
Last night I was prompted by a link to read one of Henry Eggers' CDP posts which makes me curious; how many programmers are still around who at one time worked on *Native* Pick and its variants like ADDS, Microdata, Ultimate and such? Henry Keultjes hbkeultjesatarthlinkdotnet Microdyne Company Mansfield Ohio USA |
![]() |
| Thread Tools | |
| Display Modes | |
| |