ford@amix.commodore.com (Mike "Ford" Ditto) (03/24/91)
david@kessner.denver.co.us (David Kessner) writes: > Here is a question for those C= folk: Does the Amiga UNIX use the blitter > for ANYTHING? I know that it is not used for X-- but what about scrolling the > "text-only" virtual terminals? The text console driver uses the copper for scrolling much faster than the blitter could possibly do. There are a few places that it could possibly make use of the blitter, but it doesn't yet. > Also, can someone set me straight on exactly > what video modes X will support on the 3000UX (without the U of L board). The graphics screen driver supports essentially all the standard Amiga modes. The X server uses this driver, but currently uses only one bitplane. In other words, The X server will do 1024x800 on the A2024, or 704x480 with overscan on an NTSC monitor, or the standard 640 x 400 NTSC mode, or the corresponding PAL, non-HIRES, and non-interlaced modes. I'm aware of only one notable omission: the 31kHz 640x480 "productivity" mode of the ECS. -=] Ford [=- "Look over there!... A dry ice (In Real Life: Mike Ditto) factory -- a good place to get ford@amix.commodore.com some thinking done." uunet!cbmvax!ditto - Talking Heads, "Cities" ford@kenobi.commodore.com
joey@well.sf.ca.us (Joey Paris) (04/05/91)
Greetings... I work for a Commodore Amiga dealer in New York City and we recently received the Amiga 3000UX. Setting up the Unix was quite simple and our manager had the great idea of putting it on display in the sales pit. As you would guess, when we were not looking, an unknowing customer made the system reboot without doing a proper shutdown. When we tried to get the system running again we were greeted with a flurry of DUP errors when going through the phase 1, 1b and 2 checks. This was then greeted further with the system rebooting. I know what your saying, "Just re-install the system with the tape drive!" Well, we tried that, using the Boot and Root disks. And we were greeted even further with the following: s5mountroot VOP_OPEN error 30 PANIC: vfs_mountroot: cannot mount root: errno30 Backtrace: 7C38492 7C38626 7C389A4 7C55466 7C514AC 7C00044 Kernal Root PTR: 7D15800 User Root PTR:0 ----------- Ok, so does anyone have any ideas what is going on here? The manuals have *NO* reference to error numbers or what to do in case of an inproper shutdown, nor can I believe all this is happening because of one customer pressing the wrong buttons. Please respond via email is you can be of *ANY* assistance. Thank you.