The Icon Bar: General: Trouble with booting with Access and TCP/IP enabled
| |
Trouble with booting with Access and TCP/IP enabled |
| |
bhtooefr (01:00 1/12/2012)
PaulV (01:53 1/12/2012)
bhtooefr (20:18 1/12/2012)
Bonez (19:03 16/3/2013)
PaulV (22:58 16/3/2013)
|
| |
|
Eric Rucker |
Message #121580, posted by bhtooefr at 01:00, 1/12/2012 |
Member
Posts: 337
|
Just got an A3020 (with 4 MiB RAM, for what it's worth), and decided to put a fresh !Boot structure on it. (I backed up the old one that worked, though, so I can always grab that.)
The installed !Boot is based off of http://www.retro-kit.co.uk/page.cfm/content/UniBoot-for-RISC-OS/, although I did add some updates. (Primarily TBox.zip from Castle.)
I've found that I can boot just fine with Access enabled, *OR* I can boot just fine with TCP/IP enabled. Upon enabling both of them, however, soon after I get the desktop (while still on the splash screen), I get tons of "Not enough memory in module area" errors, a few application crashes, and then the system is only in a partially usable state (many programs won't have !Booted properly when the Filer saw them, the WimpSlot is something like 170 MiB or so, and can't be adjusted). At least I'm able to *appsize 2048k, then start !InetSetup and disable either Access or TCP/IP, then reboot.
If it matters, it's an EtherLan 102 A+ ethernet card.
Suggestions for where to troubleshoot?
[Edited by bhtooefr at 01:05, 1/12/2012] |
| |
 [ Log in to reply ] |
| |
|
Paul Vernon |
Message #121581, posted by PaulV at 01:53, 1/12/2012, in reply to message #121580 |
Member
Posts: 135
|
One of the reasons I didn't build TBox.zip into the Uniboot distro on my site was because it made the system too unstable to make it worthwhile. I spent a good month sorting out versions of modules that worked well with RISC OS 3.xx and I use Access over TCP/IP regularly to get things from my Rasbperry Pi to my Arc's and vice-versa.
I'd definitely recommend re-doing the !Boot structure without the TBox.zip file and seeing how TCP/IP and Access work under those circumstances first of all.
Paul |
| |
[ Log in to reply ] |
| |
|
Eric Rucker |
Message #121582, posted by bhtooefr at 20:18, 1/12/2012, in reply to message #121581 |
Member
Posts: 337
|
Ah, that worked much better, thanks!
(Your boot structure, !SetIcons and !ChangeFSI in Boot:Resources, and an RMLoad line in Choices:Boot.PreDesktop to get FilterMgr loaded (for ArcWeb), is what I'm running now.)
[Edited by bhtooefr at 20:19, 1/12/2012] |
| |
[ Log in to reply ] |
| |
|
Bonez |
Message #122063, posted by Bonez at 19:03, 16/3/2013, in reply to message #121582 |
Member
Posts: 50
|
Thanks for sharing your solution Eric. Being relatively new to the RiscOS way I'm sure the info will come in handy to get my A4000 on line.
[Edited by Bonez at 19:17, 16/3/2013] |
| |
[ Log in to reply ] |
| |
|
Paul Vernon |
Message #122065, posted by PaulV at 22:58, 16/3/2013, in reply to message #122063 |
Member
Posts: 135
|
If it helps, I posted a full detail of configuring an Arc once Uniboot is installed over on Startdot STH Forums... It references an R260 but it's just the same as an A4000 for this purpose.
http://www.stardot.org.uk/forums/viewtopic.php?f=29&t=5486#p50857
Paul |
| |
[ Log in to reply ] |
| |
|
The Icon Bar: General: Trouble with booting with Access and TCP/IP enabled |
