HDTenEightyP/NetNews huggingface dataset:
From: grr@cbmvax.commodore.com (George Robbins)
Newsgroups: comp.sys.amiga.hardware
Subject: Re: Is it silly to buy a
Date: 12 Oct 92 19:03:13 GMT
Reply-To: grr@cbmvax.commodore.com (George Robbins)
Organization: Commodore, West Chester, PA

In article <OA92-910-103_14f3d7e5@piraya.bad.se> Thomas_Agatz@pitstop.bbs.bad.se (Thomas Agatz) writes:
> Hi Roger !
> 
> In a message of 09-Oct-92 you wrote:
> 
>  RN> system in my eyes. The A4000 is more focused on graphics, especially
>  RN> video work, and seems to sacrifice other areas of the system design.
>  RN> One area that particluary annoys at least me is the 2Mb CHIP RAM
>  RN> limit. The A4000 introduces screen resolutions which consumes four
>  RN> times as much memory, but does not offer any more CHIP RAM to store
>  RN> those four times a large screens in. I never run out of CHIP RAM on my
>  RN> A3000 during normal operation, but I can easily use 1.5Mb CHIP RAM.
>  RN> There's not much left, but it's enough. But what about if I started
>  RN> using an A4000? Then I would probably be using more flashier colours
>  RN> in most places, thus eating up much much more CHIP RAM. 2Mb would
>  RN> suddenly not be enough for normal operation -- at least I would feel
>  RN> the limit, and would be annoyed.
> 
> I had an interview with Commodore last week, where i got the chance to see
> the A4000 from the inside, and they told me that you easily could expand
> to 8mb of chip RAM.

Either that somebody from Commodore was confused, or there was a
mis-communication between the two of you on which RAM it was that
could be easily expanded.

-- 
George Robbins - now working for,     work:   to be avoided at all costs...
but no way officially representing:   uucp:   {uunet|pyramid|rutgers}!cbmvax!grr
Commodore, Engineering Department     domain: grr@cbmvax.commodore.com
From: ph2sal@sdcc14.ucsd.edu (James Lee)
Newsgroups: comp.sys.amiga.hardware
Subject: HP DeskJet 500
Date: 14 Oct 92 03:56:03 GMT
Organization: University of California, San Diego

Hi everyone.  I very recently purchased a HP DeskJet 500, but I'm
not really sure how the internal fonts work.  The printer driver I'm
using is the very one that came with WB 2.0, and the Word Processor
I tried it out with was ProWrite 3.2.3.  When I tried to print
graphics, everything seemed fine except even with the quality set
on "HIGH", the small fonts wasn't very impressive.  So I decided to
try off "draft" printing using the printer fonts.  The print menu in
ProWrite gave me 10 different font sets, but when I chose the
different font sets, it seemed to almost always give me Letter
Gothic (there's one Courier and one condensed Courier, but that's
about it besides the 12 point Letter Gothic).  In the manual it says
that the only font you could switch it manually is Courier, and all
else requires software intervention.

I guess my question is, how do I access the CG Times font in my HP
DeskJet with my Amiga using ProWrite?  Is there a better printer
driver I could use?

						--- James
						j1lee@ucsd.edu
Newsgroups: comp.sys.amiga.hardware
From: dkm@col.hp.com (Dave K. Martin)
Subject: Re: 1960?
Date: Thu, 15 Oct 1992 17:11:56 GMT
Organization: HP Colorado Springs Division


I don't have any info on the 1950 monitors, maybe some who has one can post the 
info for it.  From the Commodore "1960 MULTISCAN Color Monitor User's Guide"
page 14, here are the specs for the 1960:

	Screen Size		356mm (14 inch) diag. measure dark screen
				330mm (13 inch) viewable

	Display Area (H x W)	180 x 250 mm
				7.1 x 9.8 inch

	Dot Pitch		0.28 mm

	Line Frequency		15.75/31.5/35.5 kHz

	Image Resolution	640 x 200	640 x 480
				640 x 350	800 x 600
				730 x 400      1024 x 768 (interlaced)

	Deflection 		90 degrees

	Raster Frequency	50 to 87 Hz

	Power Supply		120 VAC +/- 10%, 60 Hz
				or
				220-240 VAC, 50 Hz

	Power Consumption	75 Watts (maximum)

	Dimensions (H x W xD)	388 x 370 x 420 mm
				15.3 x 14.6 x 16.5 inch

	Weight			14 kg (30.8 lb)

Now, with all that said, yes the display area is approximately 12 inches     
diagonal measure (I run a 690 x 720 workbench screen) which is just about 
the same size as the Magnavox 1084 clone that I was using.  The 1960 does 
have controls on the front panel for manually adjusting the height and width 
of the display as well as an auto/manual height switch. 

With the C= 2320(?) display enhancer, the hi-res interlaced images are quite
crisp.  There is no noticable flicker at any time, no ghosting or smearing of 
the pointer or other moving objects.  There is the ziper effect down the right
side of the display but that is fairly easy to ignore.  With a switch on the 
monitor cable, I can change from the Amiga display to the VGA card for my 
2088 Bridgeboard for 800x600x16, 640x480x16 or 320x200x256 color modes).  
The 1960 appears to handle the changing input frequencies with ease, locking 
up to the new display almost instantly.

(update:  Since I originally wrote this, I've added the ECS DENISE which 
          removed the zipper effect.  A severe zipper effect still shows 
          when playing some animations though.  Changing to a non-overscaned,
          non-interlaced screen for the animation fixes that though.)

The bottom line; I've had my 1960 for about four months now and am quite 
pleased with it.  
 
---
--- Dave Martin - dkm@col.hp.com
---
From: kopnicky@owlnet.rice.edu (Lyle Warren Kopnicky)
Newsgroups: comp.sys.amiga.hardware
Subject: upgradability of the A4000
Keywords: 4000
Date: 15 Oct 92 21:31:04 GMT
Article-I.D.: rice.Bw6MFt.CB0
Organization: Rice University

A question to those at Commodore: apparently, you guys designed the A4000
to be as upgradable as possible.  So what exactly can be upgraded by
changing the card in the CPU slot?  Can more chip RAM be added?  New
graphics chipsets?  Sound chips?  Obviously a new processor can.  What
else?

	Basically, what I would like to see from Commodore is a version
of the A4000, still with 2MB chip RAM, but upgradable to 8MB on the
motherboard, and everything else the same.  Is it reasonable to expect
such a thing within, say, 9 months?

+----------------------------Ren & Stimpy--------------------------------+
| "Psst. Hey Guido. It's all so clear to me now. I'm the keeper of the   |
| cheese. And you're the lemon merchant. Get it? And he knows it. That's |
| why he's gonna kill us. So we gotta beat it. Yeah. Before he lets      |
| loose the marmosets on us! Don't worry, little missy! I'll save you!"  |
+--------------- Quantum Seep -- kopnicky@owlnet.rice.edu ---------------+
Newsgroups: comp.sys.amiga.hardware
From: sanford@ee.mu.OZ.AU (sanford tong)
Subject: VXL-30...overheating?
Organization: Electronic and Electrical Engineering - University of Melbourne 
Date: Fri, 16 Oct 1992 02:58:00 GMT

	Hey, folks!

		I have a minor problem with my VXL+2Mb accelerator. In the last
3 days, we have had our warmest weather since i installed the accelerator,
with temperature of about 26 degrees (celsius). (Maybe about 30 degs inside
the room). It seems that after using the machine for about 1/2 hour, it starts
crashing with a software error->guru. From this point on, it seems to crash
randomly (usually within minutes of a reboot). If i go into 68000 mode, it runs
faultlessly.

	This setup is in an A500, with no extra internal bits other than the
accel. I suspect that it might be heat problems, since 1) the accel has worked
without any problems for about one and a half months, and decided to bomb in
the last three days, 2) the last three days have been warmer than the past
one and a half months.

	I'd be very interested in comments from anyone with a similar set-up.
(btw: i'm not overclocking the 25MHz CPU) Another interesting side-note is
that i also tried using 68000-mode-ONLY after letting the machine cool, and
although it didn't crash even after several hours, the area of the VXL board
seemed to be very warm (more than what i had noticed with the 68000 only on the
motherboard) Should the 68030 be heating up when the VXL is in 68k mode?

	If anyone has had similar experiences, please e-mail me! 

		Much appreciated!


			sanford@munagin.ee.mu.oz.au

	(btw: is there anything wrong with having a fan blowing across the
ventilation holes, as a kludgy solution?)
Newsgroups: comp.sys.amiga.hardware,comp.sys.amiga.emulations
From: barrett@karazm.math.uh.edu (Dan Barrett)
Subject: Looking for brave hardware adventurers
Followup-To: comp.sys.amiga.hardware
Reply-To: amiga-reviews@math.uh.edu
Organization: The Amiga Online Review Column - ed. Daniel Barrett
Date: Fri, 9 Oct 1992 15:02:10 GMT


	Are you a daring person who buys new Amiga hardware when it first
comes out?

	Or, perhaps, are you an Amiga hardware "power user" who really makes
his/her machine perform to its limits?

	Or maybe you are an average Amiga user who simply enjoys hardware?

	If so, then I invite you to give your equipment a thorough workout
and send the results as a review to comp.sys.amiga.reviews!  Accelerator
cards, graphics boards, MIDI and audio hardware, video appliances, freeware
hardware hacks...  no matter what hardware you're using, there are many
people out there on USENET who would be very grateful for your review.

	You don't have to be a great writer to submit a review.  In
addition, if English is not your first language, I am willing to help you
with English spelling and grammar.

	For review guidelines, write to:

		amiga-reviews-requests@math.uh.edu

or look in comp.sys.amiga.reviews, where they are posted on the first day
of every month.  Send your reviews to:

		amiga-reviews-submissions@math.uh.edu

	Remember:  everybody loves a good review.  So if you write a
good review, everybody will love you!  (Or something like that. :-))

---

   Dan Barrett, Moderator, comp.sys.amiga.reviews
   Send reviews to:	amiga-reviews-submissions@math.uh.edu
   Request information:	amiga-reviews-requests@math.uh.edu
   General discussion:	amiga-reviews@math.uh.edu
From: colin@netgate.fido.de (Colin Hirsch)
Sender: uucp@netgate.fido.de
Newsgroups: comp.sys.amiga.hardware
Subject: Re: max partition size (1.3 and/or 2.04)?
Date: 08 Oct 92  21:37:46 GMT

[7 -ct -2 ] Brent R. Earl (2:245/41.100) wrote:
 BRE> I have just added a maxtor 340meg to my amiga 2000. (gvp hc+2
 BRE> controller).  I have it partitioned into two 108 meg partitions and
 BRE> one 107 meg.  When I check with info, it reports 76m for the 108s,
 BRE> and 75m for the 107.  Any clues?  (I haven't looked under 2.04 yet).
 BRE> I also looked through the docs, and rkms and couldn't find any
 BRE> partition limits.
I don`t know what may cause your problem, but I do know, that if there are
any limits in the Kickstart you are still well beneath, as a friend of mine
has a 317 MB Micropolis HD and is happily working with a 200 and a 117 MB
partition.
Bye, Colin
**          Colin Hirsch
            UUCP: colin@netgate.fido.de
            fido:   2:245/41.9
---
From: jdp@caleb.UUCP (Jim Pritchett)
Newsgroups: comp.sys.amiga.hardware
Subject: Re: Problem using Prep w. A2090A
Date: Mon, 12 Oct 1992 07:09:53 GMT
Distribution: comp
Organization: is sometimes desirable

In article <PST.92Oct9165247@elixir.elixir.e.kth.se>, Patrik Str|mstedt writes:

> I'm having problems with my A2090A controller...
> 
> My setup: OS2.04, A2000, A2052, A2090A w. 1 MFM 40MB & 1 SCSI 20MB,
>           Adspeed, ...
> 
> I'm using my MFM harddisk as the boot partition, but since it's old,
> and not very reliable, I want to change the boot partition to my SCSI
> drive.
> 
> But... When I'm trying to prep my SCSI HD (Prep DH2:), the system hangs.
> 
> Prep (v33.34)
> hddisk.device (v34.4)
> 
> Partitions: Boot (DH0), unit 1, Cyl. 2-9, OFS.
>             DH1  (DH1), unit 1, Cyl. 10-644, FFS.
>             DH2  (DH2), unit 6, Cyl. 2-614, FFS.
> 
> Any ideas?

Yes, prep is pretty dumb.  If you specify too many blocks, prep will hang at
the last block.  Recheck your specs on the drive and try reducing the highcyl
on the last partition.


                                                Jim Pritchett


UUCP:  rwsys.lonestar.org!caleb!jdp
 or    utacfd.uta.edu!rwsys!caleb!jdp
Newsgroups: comp.sys.amiga.hardware
From: meyer@crs.cl.msu.edu (Matthew R. Meyer)
Subject: MFM hard drive controller 
Reply-To: meyer@crs.cl.msu.edu.UUCP (Matthew R. Meyer)
Organization: Michigan State University
Date: Sat, 10 Oct 92 05:22:21 GMT

hello.. I am yet another person looking for a MFM/RLL type controller
new or used, just ready to go  I would even take a PC clone 8 bit one!
(I did the bynery hack so amiga or PC 8bit would work}

reply to my account
meyer@crs.cl.msu.edu
From: jyork@iastate.edu (Justin York)
Newsgroups: comp.sys.amiga.hardware
Subject: Re: Can anyone suggest a solution?
Date: 13 Oct 92 01:19:17 GMT
Article-I.D.: pv343d.jyork.718939157
Organization: Iowa State University, Ames IA


One note: the guru error is almost always 00000004.????????
which (according to the Amiga C Manual) signifies an Illegal
Instruction. Is there a way to test for (or fix) this?
 
					Justin York
					jyork@iastate.edu
Newsgroups: comp.sys.amiga.hardware
From: 22black@sol.cs.wmich.edu (Martin E. Black)
Subject: Re: a4000 an possible deinterlacer.
Organization: Western Michigan Univ. Comp. Sci. Dept.
Date: Fri, 9 Oct 1992 05:46:37 GMT

TomK@cup.portal.com (Tom R Krotchko) writes:

>Let me ask a dumb question (this is important, as my wife has been convinced
>we really need a 4000):

>If I use ProPage in the 640x400 resolution (interlaced in all "lower" Amigas),
>will the display be interlaced? Or can I *force* any request for an interlace
>screen to be non-interlaced?

Well the display should be deinterlace or DBlNTSC, because I have read that
ProPage uses the display database for modes and would be slipped into what
would be like a productivity mode, without specifying.  But there will be 
a lot of progs that won't be so OS friendly that would be interlaced.

Martin
Organization: Penn State University
Date: Wed, 14 Oct 1992 22:54:12 EDT
From: <JBK4@psuvm.psu.edu>
Newsgroups: comp.sys.amiga.hardware
Subject: 1960?

What's the difference between the 1960 & 1950 monitors?

Jason K.
Newsgroups: comp.sys.amiga.hardware
From: mascot@bnr.ca (Scott Mason)
Subject: Re: Two A4000 questions
Organization: Bell-Northern Research, Ottawa, Ontario, Canada
Date: Thu, 8 Oct 1992 18:29:20 GMT

In article <35645@cbmvax.commodore.com> daveh@cbmvax.commodore.com (Dave Haynie) writes:
>In article <stefanb.718458688@hathi> stefanb@hathi.informatik.rwth-aachen.de (Stefan Becker) writes:
>
>>1) The A3000 supported static column RAM chips. Does the A4000 Ramsey chip
>>   support this type too?
>
>The A4000 RAMSEY supports them, but there are two problems.  First of all,
>the '040 doesn't run burst cycles,

I can't say as I've ever see Dave wrong, so I would have to ask him to
clarify this. Our '040s certainly run burst cycles (line transfers).
It even has a pin called Transfer Burst Inhibit, which corresponds to
the '030s Cache Burst Acknowledge, although it is inverted in meaning,
like so much of the '040 ;-).

>so the only advantage of SCRAM would be in
>page-detect mode, which does work on the A4000's RAMSEY but isn't a guaranteed
>performance win (though changes are, it'll be more effective with '040 than
>'030 bus activity).

If you don't explicitly support burst mode, I would expect page-detect
mode to be a big win (when the caches are enabled), since it should
still speed up transfer-burst-inhibited line transfers.

>Dave Haynie Commodore-Amiga (Cool Advanced High-End Systems You Can't See Yet)
> "The Crew That Never Rests"  {uunet|pyramid|rutgers}!cbmvax!daveh   BIX: hazy
>              "I got a pocket full of kryptonite" -Spin Doctors

------------------------------------------------------------------------
#include <disclaimer.h>                          Bell-Northern Research
Scott Mason                                      P.O. Box 3511 Station C
Internet: mascot@bnr.ca                          Ottawa, Canada, K1Y 4H7
From: mks@cbmvax.commodore.com (Michael Sinz)
Newsgroups: comp.sys.amiga.hardware
Subject: Re: New Amiga(s) Expansion/Future
Date: 9 Oct 92 12:41:05 GMT
Reply-To: mks@cbmvax.commodore.com (Michael Sinz)
Organization: Commodore, West Chester, PA

jbickers@templar.actrix.gen.nz (John Bickers) writes:
>Quoted from <67346@cup.portal.com> by Christopher_Thomas_Winward@cup.portal.com:
>
>> Who in their right mind would ever dare to develop specifically for the
>> A4000 and AA chipset when it only comes on one or two of the most
>
>    People with a specific market that can use the extra capability,
>    which funnily enough happens to be what the Amiga market is.
>
>    So let's let the professional developers decide what's good and
>    bad, eh, instead of spouting off for no particular reason.

Also, no one in their right mind will hit the AGA hardware directly but
will use the operating system.  We are not going to continue to offer
hardware-level access at our custom chips.  Why?  Well, we want to
be able to advance faster than we have in the past and this will
require (and cause) various generations of custom chips to be incompatible
in the new advanced modes.

Also, if you use the operating system the way we designed it, you can have
a program that runs under 2.0 and will automagicly know about the new video
modes in new machines (such as the A4000) and will be able to make use
of those modes/features.  The only people that will get hurt are those that
hit the hardware directly.

/----------------------------------------------------------------------\
|      /// Michael Sinz  -  Senior Amiga Systems Engineer              |
|     ///                   Operating System Development Group         |
|    ///   BIX:  msinz      UUNET:  mks@cbmvax.commodore.com           |
|\\\///    "A master's secrets are only as good as the                 |
| \XX/      master's ability to explain them to others" - Michael Sinz |
\----------------------------------------------------------------------/
Newsgroups: comp.sys.amiga.hardware
From: paws@spam.cray.com (Daniel Baehr)
Subject: You CAN connect 2 Amiga via the SCSI port..
Organization: Cray Research, Inc.
Date: 12 Oct 92 04:46:19 CDT


    I have had my 2 A2000s connected together via the SCSI port for a 
 long time now.  IVS can do it just fine!  I have a Trumpcard on my BBS
 machine and a GrandSlam in my "personal" 2000.  The setup works like a
 charm!!  

    I'm really surpised that, unless I missed one, NONE said anything
 about IVS's stuff.  I have been using their controllers for almost 2
 years now and have had the machines connected via the SCSI bus for 1
 of those two years.

    There are a couple of things you have to keep in mind.  One.  Only
 ONE device can be mounted as WRITABLE by ONE controller at a time.  If 
 more than one controller can write to a device/partition at a time you
 WILL GET R/W errors!  Two.  You CANNOT access the memory, serial port
 or any of the other resources of either machine.  ONLY THE "STUFF" ON 
 THE SCSI BUS IS AVAILABLE FOR "SHARING".  But thats NOT to say that 
 some enterprising programmer could not write a program to make my 
 statement false!! :)  It could be done.

    If anyone has any questions I'll be MORE THAN HAPPY to do my best to
 answer them......as long as they have to do with SCSI sharing and such
 .... :) :) :) :)  L8TR........



   Daniel Baehr



--
+--------------------------------------------------------------------------+
| Daniel Baehr Work: paws@spam.cray.com  Home: daniel_baehr@bearsden.UUCP  |
|              Portal: paws@cup.portal.com  -> (Public Access UNIX system) |
+--------------------------------------------------------------------------+
Xref: sparky comp.sys.amiga.hardware:16900 comp.sys.amiga.misc:15011
Organization: Middle East Technical University - Computer Center
Date: Monday, 12 Oct 1992 13:44:17 TUR
From: <E63256@TRMETU.BITNET>
Newsgroups: comp.sys.amiga.hardware,comp.sys.amiga.misc
Subject: Re: Amiga-IBm file transfer
Distribution: na
 <1992Oct4.232214.5931@dragon.acadiau.ca>

In article <1992Oct4.232214.5931@dragon.acadiau.ca>, 890530m@dragon.acadiau.ca
(Darren MacKenzie) says:
>
>FelineGrace@cup.portal.com (Dana B Bourgeois) writes:
>
>>A null modem cable is (at its simplest) just three wires:
>
>> pin 2 --\ /--pin 2
>>          x
>> pin 3 --/ \--pin 3
>
>> pin 7(?)-----pin 7(?)
>
>> Im not sure about pin 7 being the right pin.  It should be a ground pin
>>anyway.  Sorry, about this.
>
>Pin 7 is the ground pin...but it won't (or at least shouldn't) work unless
>you have a couple other pins jumpered.  Pins 4 and 5 should be shorted on
>each side (meaning pin 4 touches pin 5); also pins 6,8, and 20 should all
>be shorted on each side (6-8-20).  This should be enough, along with the
>pins listed above.
>-Doctor
>

As I saw in a abacus book the pin connection is:
2  3
3  2
4  5
5  4
7  7
From: mks@cbmvax.commodore.com (Michael Sinz)
Newsgroups: comp.sys.amiga.hardware
Subject: Re: Avoid the Amiga 4000
Date: 14 Oct 92 12:56:41 GMT
Reply-To: mks@cbmvax.commodore.com (Michael Sinz)
Organization: Commodore, West Chester, PA

jpotter@sirius.ucs.adelaide.edu.au (Jonathan Potter) writes:
>In article <n0ba0t@ofa123.fidonet.org> Aric.Caley@ofa123.fidonet.org writes:
>>> at 15Khz no matter what.  The "Promotion" feature of the OS only works for
>>> a tiny few, well-written Amiga programs, and no games.  This means that a
>>
>>And who's fault is that?  NOT COMMODORE'S!  Its the fault of the programers
>>who didnt properly write their programs.  Complain to them, not commodore!
>
>That's not strictly true. Promotion will only be applied to screens that
>open using the 2.0+ functions using tag lists. Anything written before
>2.0 will not be promoted, but this does not mean it was not well written
>software.

This is *exactly* the wrong answer!  Anything that is *pure* pre-2.0
OpenScreen() will always get promoted (if that option is turned on in
preferences)  New (2.0) software also will get promoted if they
use the old default monitor codes.

The *ONLY* programs that will not get magically promoted are:

1)  The programs that don't use the system to open the screen.  If they
    hit the hardware they do not know how to turn it on and how to handle
    the different copper lists needed...  They will not be promoted.

2)  The programs that *specifically* ask for a *specific* monitor
    using the new *2.0 and up* monitor IDs.  As it turns out, there is
    a reason why some software would want to.  For example, if you are
    writing a video titling program you need to get the display onto
    video tape or any other video-like device (TV, Cable, etc) then
    you need to get the video mode for that device (such as NTSC or PAL)
    These modes are normally the 15.75 kHz scan rate modes needed.

>Lack of a display enhancer is the only major flaw I can find in the
>4000.

Well, then, I guess there is no real flaw except in the minds of some
people who don't know better.

/----------------------------------------------------------------------\
|      /// Michael Sinz  -  Senior Amiga Systems Engineer              |
|     ///                   Operating System Development Group         |
|    ///   BIX:  msinz      UUNET:  mks@cbmvax.commodore.com           |
|\\\///                                                                |
| \XX/     "I think not." said Ren'e Descartes, then he vanished.      |
\----------------------------------------------------------------------/