gushi: (Default)
Fucking laptop is reformatted, service packed, with all the stupid sony stuff installed. My screen now dims when I yank power (to save battery). Was that so much to ask?

I've got drivers reinstalled for the USB serial port and the bluetooth -- again.

I still have a stuck HDD LED, which has to be something hitting ground or something, but I don't really care.

Wifi card is still acting a little odd, but I don't really care about that either. I think that's a firmware issue -- I'm updating now and seeing if the fucking thing behaves (I won't call it "stable" until it behaves like overnight or better).

Beyond that? All appears happy. I still need to reinstall knoppix, but getting to knoppix is as simple as "boot into dos and run a batch file". I still need to do the HD install but that's minor.

Now, on to all this work I need to actually do.

Hrmmm, dinner isn't a bad idea either.
gushi: (Default)
Yay, I've got GPRS with bluetooth working under win2k. My phone is snugly in my pocket, and laptop is connected to prime just fine.

Hrmmm, if I'm going to continue to do this, I should prolly install WinAim again.
gushi: (Default)
Yay, I've got GPRS with bluetooth working under win2k. My phone is snugly in my pocket, and laptop is connected to prime just fine.

Hrmmm, if I'm going to continue to do this, I should prolly install WinAim again.
gushi: (Default)
Okay, new annoyances.

Apparently my HD LED is now permanenly stuck on. Whether this is a BIOS bug, orsomething else, it stays on full time, even in DOS. Even in linux. Even while in the bios.

And the knoppix installer for some reason spawns qtparted, which has to be the worst disk editor I've ever seen. It temporarily ate my windows partition (although truth be told, windows shares the blame on that. You have one primary partition, you tell windows to create a second, and it says "okay, extended partition" WHY?

And it wouldn't boot because it was expecting windows to be on the SECOND partition. Grr.

Ah well, looks like Knoppix is up enough to be usable. Still have a bunch of tweaking to do on it...honestly, it's slower than I'm comfortable with under 128 megs of ram. Much as it pains me to admit that windows runs more does.

My Bootmenu:

The Good
The Bad
The Ugly


Jul. 4th, 2005 09:24 pm
gushi: (Default)
So I've followed my prvious plan, and have installed a 2g dos partition, and then for D, win2k.

In going to download the drivers from sony, I see random files failing to extract. I take winzip and crack open the "installshield" files. Where I find cab files that Winzip vomits on.

Okay, fine.

I do a little more research, I find that apparently Installshield IGNORES the microsoft standard for cab files, and uses its own. I get my hands on i6comp, a command line utility to extract THOSE cab files. And there I find them. Batch files.

INSTALL C:\WINNT\Driver\something.sys

Well, that ain't going to work, is it? My winnt folder is on D.

Frustrated, I just go into device manager and say "hey, the driver's over there", and point them at the folder I extracted everything to.

That worked for a couple things.

Of course, once I got to anything that deals with the uniqueness of this thing as a laptop (the battery util, the keyboard hotkeys, the setup utility), there's an asinine procedure you have to follow:

Before installing this utility, you must first install the following Core Driver components in the order listed below:

Sony Notebook Control Device Utility
Sony Programmable I/O Control Device (only for the PCG-C1XS, PCG-F370/F390, PCG-F420/F430/F450/F480/F490, PCG-N505VE, PCG-N505VX, PCG-XG9, PCG-XG18/XG19, PCG-Z505HE/Z505HS)
Sony Utility Dynamic Link Library
Sony Extended BIOS Dynamic Link Library

All of those are separate installers. All of them want reboots in between.

And naturally, since I have no way of knowing which installers are going to have badly written batch files in them, this is a shitload of trial and error.

On my most recent attempt, windows found a new device "SYSTEM", and asks me for a driver. I give it one, and it bluescreens on me. I've rerun SFC to make sure everything is okay, and at this point I wonder if I really *need* those hotkeys. I think it's a necessary thing, considering I can't tweak screen brightness without it. I'm going to give it one more try in a bit.

At this point, I'm downloading the Knoppix ISO. I still need to install all the GPRS stuff for my phone, and the drivers for the USB-Serial adapter, and all the other crap you need when you work on routers.
gushi: (Default)
Okay, so this thing just decided to have its hard drive say "I'm taking my gavel and going home." The drive has been making a loud "clack clack clack" noise like some teenager with a new tongue piercing this whole time. Of course, just after I bid on a new 20g drive (more than I'll ever need) on ebay, the thing froze up and went into arrest (no noise, no response, hard drive light SOLID). Basically meaning the drive stuck its fingers in its ears and said "LALALALALALA INT 14 I can't hear you".

Okay, so there should be a new drive here within a few days, and the result is probably going to be a hybrid system like I have at work: win2k/knoppix. So I've arrived at a problem

The vaio can boot from its special Y-E data USB "FlashBuster" floppy.
The vaio can boot from a special PCMCIA cdrom Like this one.The vaio can boot from the hard drive.

It will NOT boot any other USB devices. Period.

I *think* OS Loader 2000 may be the best answer to this, it claims it can boot from USB. I only HOPE that doesn't require that your bios support it as well.

Update. It requires bios support. Friggin bullshit. All I want is a floppy with a USB driver that just says "hey, that device I just found (be it a pendrive or a USB cdrom) looks bootable, I'll load it." I mean, what I'll PROBABLY do is create a small (30 meg or so) FAT16 dos partition and drop every known driver in there, but it still fucks up all these nice utilities that want to BOOT from the media. Grrr

Update-Update: This looks promising.

One way to find out -- what I would really LIKE is if there were a floppy disk that would present you with the same menu, so you don't have to permanently install OS loader 2000. But since I'll be multibooting anyway, I suppose I'll deal.

Of course, I've managed to get linux to boot just by tweaking the windows boot loader. See this screenshot.

More to come.

August 2017

678 9101112
27 28293031  


RSS Atom

Most Popular Tags

Style Credit

Expand Cut Tags

No cut tags
Page generated Sep. 26th, 2017 07:09 am
Powered by Dreamwidth Studios