[MLB-WIRELESS] Horrible pain...

[Fenn Bailey]

Thanks to everyone for the advice.

I will go home and try bashing some of those options. Failing that, it's
back to a clean install.

Cheers (and thanks again to all),

	Fenn.

> -----Original Message-----
> From: owner-melbwireless at wireless.org.au 
> [mailto:owner-melbwireless at wireless.org.au] On Behalf Of Random
> Sent: Monday, 3 June 2002 12:50 PM
> To: melbwireless
> Subject: RE: [MLB-WIRELESS] Horrible pain...
> 
> 
> 
> Rather than completely re-installing you should be able to find the
> particular patch that caused your grief.. Have a look through the
> windowsupdate install log, on the winupdate site or in add/remove
> programs. You can search the 'Q' numbers with M$ and 
> hopefully undo the
> damage by either uninstalling that manually or through add/remove (use
> with care!!).
> 
> Otherwise there is a lot of info over at microsoft.com/search about
> Win9x and its irq / io sharing issues, do some more deep 
> searching there
> (sounds like you alread have done some)..
> 
> Resource sharing with M$ is a nightmare though, another thing, try
> playing with the hardware, free up some other m/b resources, and move
> the pci cards around. Sometimes you can get lucky and Windows will
> shuffle your io's/irq's in a good way! ;)
> 
> ---
> Martin Laukkanen (random at sectoid.org)
> 
> > -----Original Message-----
> > From: Andrew Dean [mailto:ferni at shafted.com.au] 
> > Sent: Monday, 3 June 2002 11:25 AM
> > To: melbwireless
> > Subject: Re: [MLB-WIRELESS] Horrible pain...
> > 
> > 
> > Couldn't you just format the machine, and install a clean 98 
> > on it and not windows update it or whatever you did?... or 
> > even better run a better OS... 9x is a pain when it comes to 
> > resource sharing...
> > 
> > ----- Original Message -----
> > From: <fenn_b at smktech.com.au>
> > To: <melbwireless at wireless.org.au>
> > Sent: Monday, June 03, 2002 11:02 AM
> > Subject: [MLB-WIRELESS] Horrible pain...
> > 
> > 
> > > Hi All,
> > >
> > > I am finally conceding (temporary) defeat with a wireless related 
> > > problem I am having. I recently received my beautiful Ricoh 
> > > PCMCIA->PCI bridge as purchased in the bulk buy (thanks 
> Paul!) and 
> > > popped it in a machine with a lucent orinoco silver. To my 
> > delight, it 
> > > worked perfectly and all was good in the world.
> > >
> > > I then put it in a second machine, which I have a specific 
> > application 
> > > for. Unfortunately, there due to it's nature, it must be running 
> > > windows (win 98 to be precise). It too worked perfectly 
> > there as well, 
> > > until I decided to install a "Windows Update" (it was a 
> > fresh install 
> > > of 98SE), after which the orinoco WOULD NOT WORK no matter what I 
> > > tried.
> > >
> > > I'm by no means a newbie when it comes to the caveats and 
> > > peculiarities of the windows' Plug'n'pray system, but this 
> > one has me 
> > > beat.
> > >
> > > Before I get into the major rant, quick system setup summary:
> > >
> > > PC
> > >  - Intel P133
> > >  - Old Intel Triton FX chipset (concerned about this)
> > >  - 64MB ram
> > >  - Win98SE with Orinoco-wrecking-update
> > >  - Ricoh (RL5C475?) PCMCIA->PCI bridge
> > >  - Genuine Orinoco Silver (dunno about firmware)
> > >
> > > Basically, what happens is that when the machine boots 
> (or I insert 
> > > the card), the drivers all detect and install, the card 
> comes up in 
> > > the cardbus screen, but it makes a low your-card-isn't-working 
> > > "BEEEP", as opposed to the normal Card-OK beep it makes.
> > >
> > > Further investigation shows that the orinoco is sharing the I/O 
> > > address with the cardbus adapter (which I thought was OK). 
> > I basically 
> > > stuffed around with it for aaaages, until I found that if 
> I changed 
> > > the I/O address of the cardbus adapter (once booted), it would 
> > > re-allocate resources on the spot, the card would come up 
> > and it would 
> > > work perfectly. However, as soon as I reboot, the orinoco 
> > will jump on 
> > > to whatever resource I have allocated the cardbus adapter 
> > and fail to 
> > > work again.
> > >
> > > So far I have:
> > >  - Fooled with IRQ's/IO addresses till the cows come home (they 
> > > haven't
> > > yet)
> > >  - Adjusted PCI IRQ steering settings
> > >  - Reinstalled orinoco driver completely (it's running the latest)
> > >  - Reinstalled ricoh driver completely
> > >  - Found an alternate ricoh driver and tried that
> > >  - Tried taking out multiple other devices
> > >  - Tried manually changing I/O or IRQ values via the 
> > registry (device
> > > manager won't let you change it on the orinoco)
> > >  - Fooled with the EnableIRQSharing key in the orinico 
> > hardware registry
> > > entry
> > >
> > > Basically, there seems to be no way that I can find to stop the 
> > > orinoco jumping to the same I/O address as the cardbus 
> adapter, and 
> > > hence making itself completely and utterly useless. In 
> addition to 
> > > this, the BIOS on the motherboard appears to be so old it is 
> > > pre-flashable and I therefore can't do a flash upgrade (I'm 
> > 95% sure).
> > >
> > > Just wondering whether anyone else has experienced 
> anything similar.
> > >
> > > Any suggestions are most welcome (and thanks in advance),
> > >
> > > Fenn.
> > >
> > >
> > > To unsubscribe: send mail to majordomo at wireless.org.au
> > > with "unsubscribe melbwireless" in the body of the message
> > >
> > >
> > 
> > 
> > To unsubscribe: send mail to majordomo at wireless.org.au
> > with "unsubscribe melbwireless" in the body of the message
> > 
> > 
> 
> To unsubscribe: send mail to majordomo at wireless.org.au
> with "unsubscribe melbwireless" in the body of the message
> 


To unsubscribe: send mail to majordomo at wireless.org.au
with "unsubscribe melbwireless" in the body of the message