Hi Ky!
> KM> Nope, it's the Hackintosh installer, it's known to be at best
> KM> cranky. Might be a fail in its SATA driver. Will have to try it
> KM> with IDE.
> Possibility is an SATA issue: seem to remember a compatability issue at
> times.
KM> Standards, so many to choose from...
Not to mention interchangeable parts won't!
> https://www.google.com/search?client=ubuntu&channel=fs&q=Hachintosh+S
> ATA&ie=utf-8&oe=utf-8
> Top hit (or at least when I got it) might be an answer:
>
ttps://www.tonymacx86.com/threads/hackintosh-not-detecting-sata-hds.7084
KM> Leave it to Apple to be 10 years behind PC hardware. It doesn't
KM> support AMD CPUs either, tho I guess there's now a driver hack
KM> for that. Naturally I don't have IDE and Intel in the same spare
KM> box, and installing it in a VM sounds like Work. For one thing,
KM> first I'd have to install and figure out using a VM. :)
Actually the Virtual Machine, or at least the two for Linux I used,
isn't that much of a problem. (And the reason for the two is the VM
suggested and supported by Linux does only USB 1; the one from Oracle
does USB 2 and 3, so I switched to that option.) For my use the only
issue I had was at first using the default allocation of RAM (512 MB)
which caused a sluggishness in the BBS editor, sometimes severe at time,
almost to the point I thought things had locked up. One click to
allocate 768 MB seems to have solved 99% of the problem: occasionally
see a slight hesitation.
Now for what VM you need for your side.....
KM> You wouldn't believe how many error messages go by up to the
KM> point where the Mac installer finally spits up a GUI. Literally
KM> hundreds, mostly referencing internal hacks. Never let it be said
KM> Apple fixed a bug if they could paste over it instead!
I'm surprised they haven't renamed to "insect": sounds nicer than 'bug'!
> KM> Finally got ReactOS v0.4.4 to run!! tho had to install from a CD.
> Must have been and IDE CD. <gg> Hope you weren't doing something like
> I've tried to do: install a 64-bit OS on a 32-bit system!!
KM> Ooops :)
<chuckle> The Linux installer stops and puts up a error within a
minute. The problem is more me know knowing whether the hardware can
use a 64-bit OS; I've picked up some equipment with a 32-bit Windows
installed and the hardware is 64-bit.
> KM> Right now I have it set up as a dual boot with WinXP. ROS didn't
> KM> like any of my SATA controllers, but was good with a system with
> KM> an IDE port (that dying but still not needless breed). Not even
> KM> all that old (2009ish).
> Probably has nothing to do with anything but Ubuntu 16.04 (and maybe
> 14.x) have issues with dual-booting with Windows XP.
KM> I stopped even looking at Ubuntu years ago, and will never again
KM> do a Win/*NIX dual boot, so no idea. However, I vaguely recall
KM> that you need to install Windows first, then linux, so GRUB can
KM> grab everything.
In this one instance the original OS on the laptop was a Lenovo- (IBM) installed
Windows XP, so your suggested preferred sequence was XP then
Ubuntu. Only reason I sort of wanted to keep Window was because it was
on a portable machine and so the availability of a Windows OS (albeit
old) could be useful. Might go the VM path (Ubuntu with a Virtual
Machine of Windows).
I'll probably stick with Ubuntu: went that fork as the TV recording
equipment is Mythbuntu: MythTV on a pared-down Ubuntu OS. (The OS can
be upgraded to the full-blown version; a few of the Mythbuntu Frontends
can be used both ways.)
KM> ReactOS is geared toward being compatible with Windows (right now
KM> the goal is to be byte-compatible with Win2003), and runs on
KM> FAT32, so was treated as a DOS partition. Tho XP's boot loader
KM> calls it "Unidentified Operating System on Partition C" :)
Good thing wasn't limited to the 8.3 convention!! You'd have a
"UOSonPtC"!
> KM> Had to boot ROS once in "DebugFile" mode to clear some flag that
> KM> got set wrong and made it boot slow after XP was installed, but
> KM> since then it's been perfectly good.
> Good -- maybe the boot from the SERVICE partition flag? (Thinking the Ubuntu
> issue again.)
KM> No idea, but good a guess as any.
Figured I'd suggest something potentialy valid and see if it makes sense
for your side.
> KM> Anyway, lots of stuff still doesn't work, and the file manager
> KM> has Issues (actually I think it's a bug in the FAT) but what does
> KM> work looks and behaves enough like XP that there's no difficulty
> KM> switching between 'em.
> The bugs are starting to seem vary much like the ones I experienced on
> my laptop with XP/Ubuntu!
KM> Well, installing Ubuntu was your first mistake. Next time try
KM> PCLinuxOS. :)
<whimper!> ...Looking/scanning some onf the Google hits on PCLinuxOS --
may be a worthwhile consideratin for my old laptop. Knew one of the
potential problems was going to be it's memory limitations: IIRC max of
4 GB, has 3 installed. PCLinuxOS has a minumum recommended 1 GB, so
maybe...
> KM> And on the XP side, I'm being treated to the unlikely spectacle
> KM> of fullblown XP Pro SP3 using only 71mb of RAM and reaching the
> KM> desktop in 9 seconds flat. <scratching head>
> Wow!! I haven't timed my Virtual XP boot time on this Ubuntu desktop
> system but it seems to be longer and wanted about 10x that amt of RAM to work
> decently.
KM> This is on real hardware, not a VM. And a rather old HD so not
KM> getting any boost there. For comparison, ReactOS boots in 12
KM> seconds and uses around 100mb RAM. Normal XP that isn't from
KM> another planet does at best 30 seconds and ~350mb RAM. I have no
KM> idea why this one is being so economical; it looks like it's
KM> running all the normal stuff, and I've installed this exact
KM> version before without such miracles. No 3rd party drivers
KM> installed and no networking as yet, but even so it shouldn't make
KM> that much difference... even my TinyXP install uses more RAM!
I think you have a decimal point playing tricks on you! <gg> (Semi- referencing
an old joke about an accountant miscalculating because he
thought a particle from an eraser was a decimal point,)
KM> XP64, on somewhat faster hardware, takes about 90 seconds to boot
KM> and uses around <looking> 400mb RAM (tho it has all its drivers
KM> and networking, and has presently been up for about six weeks).
OK - I don't feel so bad waiting. :) ...BTW, speaking of boot speeds,
I recently installed a 'new' printer server. (For anyone else reading
this it is device which 'translates' a network address for use by the
USB printer, so instead of relying on a specific computer the USB
printer is independant.)
Old printer server which I got years ago, was frequently horrendously
slow: sometimes several minutes before the printer turned on. (The
problem was under XP and then Ubuntu.) Also would constantly drop out,
requiring a power boot (of the server). The new server has not
experienced a drop out, plus the printer wakes up within a few seconds (longest
I've counted was 14).
» «
» Barry_Martin_3@ «
» @Q.COM «
» «
... I just had a spiritual growth removed.
--- MultiMail/Win32 v0.47
■ wcECHO 4.2 ≈ ILink: The Safe BBS ■ Bettendorf, IA
■ RNET 2.10U: ILink: Techware BBS ■ Los Angeles, Ca ■ www.techware.dynip.com
--- QScan/PCB v1.20a / 01-0462
* Origin: ILink: CFBBS | cfbbs.dtdns.net | 856-933-7096 (454:1/1)
|
