Hey, how the heck are ya? Great, now please lets not get into a pissing fight... we're on the same side, eh?
First, on a DIR, the packet.inf from the old drivers looks a lot like this on my system...
PACKET INF 3,009 08-25-00 9:10a PACKET.INF
the DIR for the packet.inf from the new drivers looks like ...
PACKET INF 2,918 03-08-01 11:40a PACKET.INF
Just on a DIR they're not identical... install doesn't work for packet.inf on the new drivers, however if you open em up, they have the same content, the packet.inf for the new drivers was saved in a rich text (or some other slightly compressed) format.... it's not pure ascii text... you can edit via wordpad, select all, copy and paste into say notepad then save a valid copy of packet.inf suitable for installing... they have the same text, but aren't the same due to compression in the newer drivers version. They expand in a word processor to the same stuff!
Next, onto a brief discussion of my warplink experiences...
1) The position of the warplink driver in the usb when changed appears to really adversely affect it under Windows 2000... to the point that W2K doesn't ever boot sucessfully... the solution/workaround is either static USB ports or addition of the warplink device after boot.
2) Once installed and running the stuff is great!
Now please, lets be nice to each other