Browsing this Thread:
1 Anonymous Users
|
Re: 68k emulation support/janus
|
||||
|---|---|---|---|---|
|
Not too shy to talk
![]() |
I spent most of the night and part of this morning playing around with various ways to configure the AROS software. I dug up my old Amiga Forever CD from 2008 and the Amiga softwsre seemed to trsnsfer over without problem, but I am still having one giant glitch. AROSi386 and AROS68x both hvae identical screens but the AmigaOS screen keeps coming out interlaced. so basically evreything is half as big and spread out twice as far. That does cause some problems and I can't find the switch to fix it.
I have made some further observations about making the system more "user-friendly" and am thinking of making a "wolfy's special iso" but need to fix this dang screen glitch first. I am also finding AROS68k to be the slowest and most unwieldy of the three in any config I have tried so far. From Wolfy, sent using OWB from inside my AROS Virtual Machine, :)
Posted on: 2015/5/6 16:19
|
|||
|
||||
|
Re: 68k emulation support/janus
|
||||
|---|---|---|---|---|
|
Not too shy to talk
![]() |
What would really top this off would be a wine port. yes the pun was intended. I just found a "clean" OS3.9 installation with boing bags. It would be a completely fresh install copied from my A3000. I might just need to remove some hardware drivers and maybe the AmiTCP stack, not sure what else.
Posted on: 2015/5/5 0:18
|
|||
|
||||
|
Re: 68k emulation support/janus
|
||||
|---|---|---|---|---|
|
Home away from home
![]() |
Hi Wolfy,
With OWB and Janus both running the memory level seems pretty right. With OWB of course it does depend on what web-page is being looking at; some web designers are definitely assuming memories in the GB for the client machines. On my netbook I'm running 1 GB, which is normally perfectly sufficient (I have Janus set to 256 MB fast, 8 MB chip), but the way some web pages are going I'm thinking I'll need to go to 2. Never played with Scalos, but it should be possibly to get WB3.1+ running under Janus; my install is a CBM kickstart 3.1 and WB 3.5. The thought of setting up the emulation separately and then pulling it into Janus is definitely sensible; my install orginally came over from WinUAE (which I am very pleased to say I haven't had to use for years now, not because of WinUAE, which is a phenominal program, but because AROS has freed me from having to use Windows as my main OS). Just keep the winding up the Clockwork Angels and it will soon be running smoothly... Cheers, Nigel.
Posted on: 2015/5/4 9:21
|
|||
|
||||
|
Re: 68k emulation support/janus
|
||||
|---|---|---|---|---|
|
Not too shy to talk
![]() |
I was goofing around trying to get fusion, shapeshifter, pc-task and PCx to run under janus/Aros68k. I have some old preinstalled hardfiles, and I think if I were to install the software properly (in the startup-sequence, et al.) I might get something. It might be better to try it under Janus/AOS68k, but I messed up the install of that and haven't fixed it again. I'm wanting to get a paired down version of my old OS3.9/Scalos system running as main screen with both AROS running on the Scalos screen.
Posted on: 2015/5/4 6:05
|
|||
|
||||
|
Re: 68k emulation support/janus
|
||||
|---|---|---|---|---|
|
Home away from home
![]() |
Quote:
Which is wrong. Everyone should know that x86 is one of the ISAs with the most code density. Take a look at some peer-reviewed articles: http://www.lsc.ic.unicamp.br/publications/ecco2009sbac.pdf http://www.eetimes.com/discussion/other/4024933/Code-compression-under-the-microscope There should be some other reasons for the increased memory consumption that you're taking about. Which, again, aren't related to the x86 ISA.
Posted on: 2015/5/3 6:29
|
|||
|
||||
|
Re: 68k emulation support/janus
|
||||
|---|---|---|---|---|
|
Not too shy to talk
![]() |
Yah, I like to push the limits of machine & man... I like the band, Rush, also. I didn't intend to be mean to the programmers who work on AROS/Icaros. Everyone knows it takes 10x as much RAM to do anything on i386!
Seriously though. I gave AROS/Acaros half of a gig of RAM under VMWare. Currently, Wanderer i386 is showing 183.9 megs left. I'm typing this in OWB. I'm running Wanderer and not Dopus Magellan. Never liked Magellan. Note- I do like Wanderer's back button on the window. I would suggest, if possible, a Forward button and a search button on the wanderer windows. But I'm digressing once more. I also run AROS68k/nogui at startup with transparency and coherency, etc. AND I'm doing it all on a VESA 1600x1200x24bit display. So the system is now booting up an extremely powerful and seamless triple OS combo, It is a tad touchy still. In other words, it crashes often and unexpectedly. the PSI Screen caller under AROS i386 absolutely refuses to work. I would just love to take all the time in the world to test everything repeatedly to find what patterns or series of events caused each crash and then reinstall/reorganize/rename all the various programs to take fullest advantage of it. hmmm, I wonder if the old 68k scalos wb can be installed/ran under AROS68k. Maybe, I'll need a gig of RAM by the time I get it all working the way I want it, lol. This is still just a taste of what I had with my A3000/ 040 warp engine with 32 megs of Ram. I am missing a lot of my old programs and utils and commodities. I would really like to see Scalos again. The new builds are supposed to run under AROS i386, but I had no luck with Icaros 1.5 or 2.03. The old distros worked with OS3.1 and higher, but again I haven't had much luck getting it to install as the wb replacement for AOS68k either. If I do find a way to install Scalos under AOS68k, then I thought I would try forcing AROS i386 to open without a gui (only a hopefully unnecessary shell) and auto start AOS68k with Scalos as the Workbench replacement. If that works the way I think it does, then the system and everything else should use the AOS68k/Scalos screen. That would be a better deal. Maybe I need to use the emergency boot and setup a separate and clean AROS68k emulation under VMWare to do the installing and testing and then it should be a simple matter of doing under janus. It would be interesting if nothing else. I have another interesting idea to make AROS more transparent to windows (and other hosts too). I thought of a way that, if it works, would make AROS act & feel a lot more like Wine on Ubuntu. I need to go find the suggestion box.
Posted on: 2015/5/2 23:15
|
|||
|
||||
|
Re: 68k emulation support/janus
|
||||
|---|---|---|---|---|
|
Home away from home
![]() |
That's a lot of ram; what's running here exactly? When I launch into the OS I generally see about 150 MB used, but of course that includes ram for the video, and that's at rather a much higer resolution than the classic. If OWB is running I can see that memory would drop significantly, but then again it is a lot more complex, and capable, than 'classic' browsers.
Cheers, Nigel.
Posted on: 2015/5/2 22:12
|
|||
|
||||
|
Re: 68k emulation support/janus
|
||||
|---|---|---|---|---|
|
Not too shy to talk
![]() |
yeah, I see that now with the fast ram. I was switching between OSes and interfaces so much, they all started looking the same. I do notice that AROS is a memory hog as well, eating up 320megs of RAM to do what the original may have done in 32. :)
Posted on: 2015/5/2 21:37
|
|||
|
||||
|
Re: 68k emulation support/janus
|
||||
|---|---|---|---|---|
|
Not too shy to talk
![]() |
Going back to that issue where janus does not have network/internet support: I'm not nearly the expert I once was in all the scripting and such, but I seem to remember using a script (possibly Arexx but maybe just Dos) that launched a program (in this case AWEB) and used a "pipe:' to bypass the emulation and feed the connection directly to the program that needed it. Is that possible in this case? I think I had to do it to get Win95 running under PCTask to use the host Amiga's connection, but it's been a decade and a half at least so I could be remembering something else altogether.
Posted on: 2015/5/2 21:35
|
|||
|
||||
You can view topic.
You cannot start a new topic.
You cannot reply to posts.
You cannot edit your posts.
You cannot delete your posts.
You cannot add new polls.
You cannot vote in polls.
You cannot attach files to posts.
You cannot post without approval.
You cannot use topic type.
You cannot use HTML syntax.
You cannot use signature.
You cannot create PDF files.
You cannot get print page.





