Partition Manager
Pages: 1 ... 13 14 15 16 17 18 19 20 21 22 23 24 25 26 27 28 29
Raik (463) 2062 posts |
Thanks for clarify. |
Jon Abbott (1421) 2652 posts |
Yes, I was referring to ADFS v4. In particular checking that it formats the correct drive and that formatting 4K drives works. I certainly wouldn’t use Partition Manager with working drives – unless you don’t mind losing them…not until its had more community testing. Even if I had every variety of hardware, there’s no way I could thoroughly test Partition Manager as it covers so many File systems, Podules, OS versions, drive types and partition types. I think it’s going to be a case of testing the obvious things and hoping everything else is good! |
Raik (463) 2062 posts |
Format an extFAT 64GB device to FAT32FS via Partition Manager was also working without problems. |
David J. Ruck (33) 1639 posts |
Exactly why I didn’t put support for fixing partitions in DiscKnight. The best I could offer for cases of partition corruption was to search for the Filecore partition on the disc, and copy all the data off to somewhere else. |
Jon Abbott (1421) 2652 posts |
Partition Manager v0.98 available for testing here |
Bryan (8467) 468 posts |
Why does PartMgr (0.98 and others) ignore the flag – Don’t allow windows off screen 0.48 behaved itself. |
Anton Reiser (471) 63 posts |
With RO 5.24 on the Titanium I get: With RO 5.29 on RPi it’s o.k. |
Martin Avison (27) 1503 posts |
What is BASICPM ? What does *Help BASICPM say? RO5.24 is rather old now, but I cannot remember a BASICPM. |
David Pitt (9872) 364 posts |
It is a Module provided by PartMgr. It is possibly something to do with the mathematical capabilities of BASIC, or some other reason. If the setup in !Run is bypassed and !RunImage directly double clicked on then PartMgr lights up nicely on OS5.24 on this Titanium. Disc sizes are correctly reported but then the biggest is only 240GB |
Martin Avison (27) 1503 posts |
Oh yes, I see BASICPM in !PartMgr. However, from my reading of the !Run file, it is only used if BASIC 1.85 or later is not running. In that case, it should have been BASICPM32 that was loaded, not BASICPM. Both modules seem to provide the BASICPM command, and are called BASICPM when loaded. Maybe Anton could load the standard BASIC 1.85 module? Here, on this Titanium, if I load BASICPM32 and then try
Caused by r1 not being word aligned? |
Rick Murray (539) 13872 posts |
I’ve just had a try of PartMan v0.88 to see if I could shed any light on what’s going on with the 128MB system memory and… It correctly has the FAT part within the FileCore part, but why “Reserved”? That’s probably best just omitted given the frankenstein arrangement of how FileCore and FAT dance together on these machines. ;-) |
Stuart Swales (8827) 1359 posts |
Smells like
So needs to be built with the SupportARMv6 option to create an aligned address for the LDM |
Raik (463) 2062 posts |
I use 5.28 and BASIC is 1.81. I get the same error message like Anton.
If I change RMEnsure BASIC 1.85 in !Run to 1.81 all I try is working. |
Jon Abbott (1421) 2652 posts |
Thanks for the reports. I added a bespoke build of 32-bit BASIC 1.85 to get it running on the A9home, but as you’ve all noticed its the ARMv4 version. I’ll correct in due course. Commenting out the lines that check the BASIC version in !Run should switch it back to ROM BASIC.
It allows the window to move off-screen, which is primarily for legacy machines with low resolutions. If it’s causing an issue I can make it resolution dependent, so it’s only allowed off-screen on low-res desktops. |
Bryan (8467) 468 posts |
No issues. It just seemed odd that an App can bypass system settings. |
Jon Abbott (1421) 2652 posts |
Should be fixed in the build I’ve just uploaded |
Anton Reiser (471) 63 posts |
It works now on my Titanium too. |
Raik (463) 2062 posts |
Here also. |
Jon Abbott (1421) 2652 posts |
What filesystem do the USB devices appear as? If it’s SCSIFS, could you post a debug log so I can see what it did.
It’s in the partition table as a Reserved partition, so it gets shown. |
Raik (463) 2062 posts |
A9home supports MassFS, DOSFS and WIN95FS… PartMgr see nothing. |
Jon Abbott (1421) 2652 posts |
It will be MassFS I suspect, which PM doesn’t currently know about . If you could eMail me a copy of the relevant FS Module and it’s associated Filer Module, I can look at adding it. |
Jon Abbott (1421) 2652 posts |
I’m close to releasing the Partition Manager build that will create a usable Pi drive, although I have an issue with AcornHTTP I’ve yet to figure out. AcornHTTP has a dependency on !Boot which is preventing hot-swapping over the SD card so a new one can be formatted. When the Module loads, it tries to access several files in !Boot, but the worst issue is URL_GetURL/URL_ReadData fail if !Boot isn’t accessible. Short of creating a bespoke AcornHTTP that works when !Boot doesn’t exist, I’m not sure how to proceed. PM needs to connect to sites to pull down HardDisc4, the Pi firmware and various packages that need pre-installing for the new OS drive to be usable when booted. And on the subject of HardDisc4. As it’s a generic HardDisc4, there are several issues with it that make it unsuitable for a Pi out of the box, for example:
To end up with a usable SD card, I’m having to alter various things such as adding the missing TimeSetup into RO520Hook and RO530Hook (it has to go here because Choices.Boot is copied from these on first boot), reconfiguring !Internet for DHCP and pulling down and installing packages such as !PackMan etc. For the minute I’ve hardcoded all of this, but I really need to create a full package manager so you can select which packages you want pre-installed onto the SD card. For the minute I’ve just added the bare minimum. All of this is working…I just need to find a workaround for AcornHTTP’s dependence on !Boot for it to be usable on a Pi. |
Rick Murray (539) 13872 posts |
Create a RAMdisc of a useful size, then hijack the Choices variables to point to the RAMdisc, so the fetcher can do whatever without messing with the SD card. |
Jon Abbott (1421) 2652 posts |
Although initialising a Pi Boot drive will fail at the download stage, due to the AcornHTTP !Boot dependency I’ve mentioned above, I’ve put Partition Manager v0.99 up for testing. I’ve detailed the caveats and known issues in the download link. I’ll continue to look for a workaround to the !Boot dependency before a final release. In the meantime, you can perform a full Pi Boot drive initialise with a drive attached via USB. |
Bryan (8467) 468 posts |
Hi Jon. I have just just used 0.99 to create a Pi Boot drive on a Pi 4 and I am now using Netsurf 3.10 to post this. So, good progress. However, I have the following comments on the contents of the Boot Loader directory (specifically for a Pi 4) - I did not find a Cmos file, so I copied one from elsewhere - Bootcode.bin is not needed on a Pi 4, so I deleted it. - Start.elf is not needed on a Pi 4, so I deleted it. - Fixup.dat is not needed on a Pi 4, so I deleted it. - I replaced the following files from a known good Pi 4 boot SDcard config.txt, fixup4.dat, start4.elf Without the above changes, I was getting nowhere towards a workable system. The screen was fixed at an workable low resolution. With the changes, this RISCOSPi2 SDcard seems good. I had no trouble with hot swapping the SDcard for the download. |
Pages: 1 ... 13 14 15 16 17 18 19 20 21 22 23 24 25 26 27 28 29