20 October 2010, 01:36 | #1 |
Registered User
Join Date: Oct 2010
Location: Thessaloniki/Greece
Age: 44
Posts: 117
|
boot problem pfs
hi , i made a hd using winuae with : OS 3.9 classicWB PFS3 filesystem , on winuae it boots and everything works ok but when i try the hd on real amiga with 4-Device Buffered IDE Interface it doesn't boot :/ (the hd is 4gb) (i have not installed yet the idefix 97 on the hd,maybe this is the problem?),any help welcome
|
20 October 2010, 08:06 | #2 |
WinUAE developer
Join Date: Aug 2001
Location: Hämeenlinna/Finland
Age: 49
Posts: 26,523
|
HD is probably slightly over 4G. Make sure all partitions are inside first 4G.
PFS3 super block is in last block of the partition, no access = no mount. |
20 October 2010, 08:27 | #3 |
Registered User
Join Date: Jan 2002
Location: Germany
Posts: 7,002
|
Super block? This is not SFS. PFS keeps all its meta information in the beginning of the partition. It does not access the last block. It even mounts successfully if the partition is defined twice as large as the hard drive.
|
20 October 2010, 08:46 | #4 |
WinUAE developer
Join Date: Aug 2001
Location: Hämeenlinna/Finland
Age: 49
Posts: 26,523
|
I mixed SFS and PFS3..
It might be incompatible HD (Amiga IDE is not 100% compatible), it is usually good idea to test the HD or CF by connecting it, booting from some install disk (that includes HDToolBox) and checking that HDToolbox detects it. |
21 October 2010, 00:04 | #5 |
Registered User
Join Date: Oct 2010
Location: Thessaloniki/Greece
Age: 44
Posts: 117
|
the hd is ok cause if formatted with ffs it boots fine in amiga , i'll try things out and see (no time today ) ,if i solve it i'll report back thanks
Last edited by _psy; 21 October 2010 at 00:48. |
21 October 2010, 21:41 | #6 |
Registered User
Join Date: Oct 2010
Location: Thessaloniki/Greece
Age: 44
Posts: 117
|
i made a smaller 1st partition 500mb (pfs formatted on winuae)and another one 3.5gb(pfs formatted on winuae) and booted ok in real amiga but it doesn't recognize the 3.5gb partition :/ (the pfs tools check disk ok but the os says it is uninitialized?) , i will format it again on real amiga and see.
Now i install idefix for the cdrom and after install it doesn't boot (black screen) , another problem to solve :/ bye |
21 October 2010, 22:07 | #7 | ||
Registered User
Join Date: Jan 2002
Location: Germany
Posts: 7,002
|
Quote:
Btw, when using WinUAE, when adding the HDD, change controller from UAE to IDE0. This way you will experience possible problems already in WinUAE and not only on the real Amiga. Quote:
Anyway, you don't need the complete IDEfix package for a CD drive. Only atapi.device in devs and CD0 in devs/dosdrivers. |
||
23 October 2010, 17:07 | #8 |
Registered User
Join Date: Oct 2010
Location: Thessaloniki/Greece
Age: 44
Posts: 117
|
hello , thomas the HD is 4.3gb seagate(not CF) and finally i decided to make one 500mb partition ,one 1.7gb and one 1.3gb and install CWB ADVSP.
(all sum below 4gb cause i can't make my CWB3.9(with pfs installed) and CWB ADV SP(with pfs installed) install recognize partitions over 2gb and sum over 4gb , on CWB ADV SP i copied the file scsi.direct(patched last version) from myfiles 128gb support and the amiga doesn't boot (displays the screen with the floppy as i had no HD on boot). Finally i partition the HD with HDToolbox (classicwb OS 3.9 with pfs installed) on winuae then i booted to classicwb adv sp(with pfs installed) on winuae and format the partitions with pfsformat ,copied all the data from virtual hd to real first partition , installed the hd to amiga and all works fine at last , then i copied atapi.device in devs (from idefix as you suggested) and edit the tooltips in CD0 icon (devs/dosdrivers) to atapi.direct from scsi.direct that was before, now i can mount CD and all my partitions works fine thanks Toni and Thomas for the suggestions [and how can i tell that i run PFS now? and not FFS ? on HDToolbox it says that my parttions are custom file system etc... and i format them with pfsformat but when i right click to DH0 icon info it says FFS int] Last edited by _psy; 23 October 2010 at 17:13. |
23 October 2010, 17:47 | #9 | |
Registered User
Join Date: Jan 2002
Location: Germany
Posts: 7,002
|
Quote:
|
|
23 October 2010, 19:00 | #10 |
Registered User
Join Date: Oct 2010
Location: Thessaloniki/Greece
Age: 44
Posts: 117
|
alright i think it's ok
|
23 October 2010, 20:17 | #11 |
Registered User
Join Date: Jan 2002
Location: Germany
Posts: 7,002
|
You didn't read the installation instructions for PFS. DosType should be PFS3, not CFS0.
|
23 October 2010, 20:55 | #12 |
Registered User
Join Date: Oct 2010
Location: Thessaloniki/Greece
Age: 44
Posts: 117
|
i think i do it right ,i partition my disk with hdtoolbox(os3.9) and added new filesystem pfs3(after the installation of pfs3 files on hd but it shows like custom in the programs ,i'll take a look again
|
23 October 2010, 21:27 | #13 |
Registered User
Join Date: Jan 2002
Location: Germany
Posts: 7,002
|
The instructions tell you to overtype 0x43465300 by 0x50465303. You didn't do this.
CFS stands for "Custom File System", but actually it means "user didn't read instructions carefully". 0x = hexadecimal numbers follow 43 = ASCII code for C 44 = ASCII code for D 46 = ASCII code for F 4F = ASCII code for O 50 = ASCII code for P 53 = ASCII code for S |
24 October 2010, 00:17 | #14 |
Registered User
Join Date: Oct 2010
Location: Thessaloniki/Greece
Age: 44
Posts: 117
|
you are right, i fixed it now ,this has any value or is it cosmetic only? and yes i was on the fast install side with many combinations to try what i like best so i was a little confused (modern hardware and windoze don't require much thinking-reading ,i need a little time to get used to!)
Last edited by _psy; 24 October 2010 at 01:07. |
24 October 2010, 08:33 | #15 | |
Registered User
Join Date: Jan 2002
Location: Germany
Posts: 7,002
|
Quote:
Also some file systems depend on the identifier to activate some features. For example FastFileSystem uses the identifier to distinct between OFS, FFS, INTL, DirCache and LongFileNames. SFS uses the identifier to activate either SFS V1 or SFS V2. FAT95 uses the identifier to assign the PC partition which should be mounted. And finally you make a fool of yourself if you show someone the report with CFS0. |
|
20 March 2017, 05:26 | #16 | |
Registered User
Join Date: Mar 2017
Location: NYC/USA
Posts: 60
|
Thomas - yet again you've helped me. You are a godsend, even if I didn't read instructions carefully. Usually I just take the information and go boom, but I gotta give props, man. Thanks!
Quote:
|
|
Currently Active Users Viewing This Thread: 1 (0 members and 1 guests) | |
Thread Tools | |
Similar Threads | ||||
Thread | Thread Starter | Forum | Replies | Last Post |
Strange problem with ClassicWB 3.9 on SFS or PFS boot partition | Tarel78 | project.ClassicWB | 15 | 20 April 2012 07:56 |
A4000 boot problem | cyberfox_it | support.Hardware | 2 | 31 March 2011 09:06 |
A500 Boot Problem | scrappysphinx | support.Hardware | 2 | 07 March 2008 10:31 |
PFS 5.3 or PFS 5.1 CD with valid Key ?? | ruliovega | request.Apps | 1 | 30 December 2005 23:54 |
Help with boot problem | Giana | support.Apps | 24 | 28 March 2003 10:40 |
|
|