10.1 Update Issues

**Dradts** · October 18th, 2001, 08:24 AM

Oink!

Before I did a clean install of MacOS X 10.1, I installed the update over my old 10.0.4. After a restart, the following things smacked into my face:

1. CD ROM support wuz broken. The 10.1 Finder wuznt even able to recognize the OS X 10.1 installer CD and asked me, whether I wanted to initialize it.

2. Apache WebSharing didn't work anymore.

3. I had a user called "unknown user" in my Login Window, but I coulnt see this user in the user control panel.

4. Most Screensavers didn't work anymore.

After I clean installed 10.1, everything worked fine again. I can now even read my old CDI MPEG movie CDs. Pretty cool

Seems like there are some bugs left in the 10.1 updater. I wanna know, what problems u had after doing an update from 10.0.x to 10.1 (UPDATE! NOT CLEAN INSTALL! CLEAN INSTALL WORKS JUST FINE!)

**Jadey** · October 18th, 2001, 10:13 AM

The apache problem occurs if you had been running 10.0.4 and installed the latest web sharing update. If you did that, apache would be broken under x.1, but the fix is simple, just a small change to your httpd.conf file. Here's the forum thread where this fix is discussed:
http://www.macosx.com/showthread.php?threadid=6899

**Dradts** · October 18th, 2001, 11:17 AM

I already looked at this thread when I recognized that my Apache was broken. N I wuz also able to get it to work again.

But whut I mean is, that the 10.1 updater should have to fix this problem, and not the user who updates!
Anyways, this ain't the only bug that is 'included' into the OS X updater....

**twister** · October 18th, 2001, 01:28 PM

with the exception of the ppp jitters its great.

twister

**ElDiabloConCaca** · October 18th, 2001, 02:36 PM

Sherlock was broken for me after the 10.1 update... so was Classic.

A) Sherlock wouldn't launch with the Cmd-F command. Clicking on it in the dock wouldn't launch it either. Neither would navigating to the file and double-clicking. I made absolutely no modifications to Sherlock at any time to warrant this. Just broken.

B) Every time I tried to start up Classic, I'd get the old "Some files need to be added..." blah blah blah... I hit ok, then it would just quit. Never could fix it, even by removing all the old extensions -- even booting Classic with "extensions off" wouldn't work. Weird.

So I re-installed 10.1 with the clean-install option (over my existing 10.1 install! Apparently 10.1 will update 10.1 also!)... weird, it didn't go through the whole formatting process, it just started installing. But, it DID clean install, as nothing was left but the 10.1 install and I had gigs of HD space I hadn't seen in ages. So I optimized with Norton with the "wipe free space" option, and everything is peachy and cool.

Problems fixed, no problemo. I highly recommend clean-installing if you can afford it.

**AdmiralAK** · October 18th, 2001, 05:59 PM

I was having modem problems but fixed them

**ElDiabloConCaca** · October 18th, 2001, 11:17 PM

What kind of modem problems? Were you using the "Apple Internal Modem 56k" script and it wasn't working or something?

Once I updated to 10.1, that script no longer functioned for me... the modem would just fail at every connection attempt -- no sound coming through the speaker, no connection, and, I'm assuming, no dialing... I'm using the Supra 56k script now with success, although the sound is a bit quiet coming from the speaker...

**Dradts** · October 19th, 2001, 05:40 AM

I hope the next update (10.2?) will work better. I don't wanna do a clean install everytime I install an update on MacOS X.

Btw, yesterday I read an article in MacLife about the new G5 proecessors. N it said, that Apple probably would trim OS X 10.2 to run wit 64bit n the G5. I hope they will then still give out 32bit versions for older g3 and g4 macs...otherwise everybody'd have to buy a new g5 mac

Anyways its cool. They will run wit maximum 1.8ghz!!!

Imagine a quadruple 1.8ghz G5 Mac!!! I would sell my girlfriend for that

j/k!!!