From owner-freebsd-questions@FreeBSD.ORG Tue Mar 29 16:23:30 2005 Return-Path: Delivered-To: freebsd-questions@freebsd.org Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id 8935516A4CE for ; Tue, 29 Mar 2005 16:23:30 +0000 (GMT) Received: from smtp11.wanadoo.fr (smtp11.wanadoo.fr [193.252.22.31]) by mx1.FreeBSD.org (Postfix) with ESMTP id 0961C43D49 for ; Tue, 29 Mar 2005 16:23:30 +0000 (GMT) (envelope-from atkielski.anthony@wanadoo.fr) Received: from me-wanadoo.net (unknown [127.0.0.1]) by mwinf1109.wanadoo.fr (SMTP Server) with ESMTP id 3731F1C00052 for ; Tue, 29 Mar 2005 18:23:29 +0200 (CEST) Received: from pix.atkielski.com (ASt-Lambert-111-2-1-3.w81-50.abo.wanadoo.fr [81.50.80.3]) by mwinf1109.wanadoo.fr (SMTP Server) with ESMTP id C918F1C00042 for ; Tue, 29 Mar 2005 18:23:28 +0200 (CEST) X-ME-UUID: 20050329162328823.C918F1C00042@mwinf1109.wanadoo.fr Date: Tue, 29 Mar 2005 18:23:27 +0200 From: Anthony Atkielski X-Priority: 3 (Normal) Message-ID: <1651925454.20050329182327@wanadoo.fr> To: freebsd-questions@freebsd.org In-Reply-To: References: <42480F8B.1060405@makeworld.com> <1648629793.20050329122346@wanadoo.fr> <42496060.1060404@makeworld.com> <467487023.20050329162852@wanadoo.fr> MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 7bit Subject: Re: Anthony's drive issues.Re: ssh password delay X-BeenThere: freebsd-questions@freebsd.org X-Mailman-Version: 2.1.1 Precedence: list Reply-To: freebsd-questions@freebsd.org List-Id: User questions List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Tue, 29 Mar 2005 16:23:30 -0000 Bart Silverstrim writes: > If a machine with a gig of memory runs fine under DOS but actually has > a bad big of memory hardware near the 512 meg address range, it would > probably still run "flawlessly" for a very very long time... This machine has 384 MB of very expensive RAM, and all of it was used by Windows NT. > But if you swap the hardware with a replacement and it works, how do > you explain Windows being broken when that would suggest it was the > hardware that was broken? I don't recall ever swapping anything. I have no reason to believe that a hardware failure has occurred. > You never put it on another identical Vectra to prove it was > reproducible. Why does it have to be reproducible on another machine? It doesn't work on my machine, and that's sufficient. If you can tell me what all the error messages mean, then please do so. If you can't, you're just throwing darts. > The problem being asserted is that the hardware was tweaked. The > firmware microcode. No assertion is worthy of my time unless it is preceded by an explanation of the exact meaning of all the error messages I'm seeing. > Really? Windows XP must be broken. I can't install it on my Mac. Swap out the hardware and see if it goes away. See if you can reproduce the problem on another Mac. It's possible that Windows uses the hardware much more efficiently than the Mac OS X, and it doesn't run on your machine simply because you have a hardware failure that OS X couldn't detect. > Fine. FreeBSD is broken. Reinstall Windows and stop complaining. I'd rather fix FreeBSD. > PS-if you can still get a driver for the timex Ironman triathlon watch, > care to share the link? I can't seem to find it anymore for the > Windows 2000 system to work without some IR interface...I wanted to use > the screen to update it still...or is Windows broken because I can't > use it anymore? Did it ever work on Windows NT-based systems? All I recall is that it looked like a custom-written trigger for photosensitive epilepsy. -- Anthony