JasonGW

RSX you mean? No, then, according to the specs it looks closer to a 7600GT. It has the same crippled 128bit memory bus (7800GTX is 256bit, and you can't underscore the impact of halving the bandwidth), is closer to the same clock speed (originally 550Mhz, recently dropped to 500Mhz, actually 60Mhz *beneath* the 7600GT), etc. Anyway, point being that PS3--much like Xbox 360--simply *isn't* as powerful as a current high end PC, it's closer to a mid-range system. Jason

Well, the bad news is that it's made zero difference, *sigh*. My clients all point solely to my AD server for DNS and still, disconnection happens every 30 seconds or so. Very freaking annoying. Jason

No worries. Any other clues? Still happening, even after moving the **** DHCP over to the WRT54G. Have you tried any of those open source firmware swaps? Any idea if they're any good? Jason OK, here's something I'm trying and I'll see if that helps or not: I've removed DHCP from the router and put it back on the server, but what I've done is modify the scope so that the clients point solely to the internal server for DNS, with the router as nothing but the gateway. I've also setup the server to do DNS forwarding (hopefully the router will let the DNS server forward requests, but I don't see any reason why it wouldn't...) so that all DNS activity should be directed to the internal server first and foremost. I'll report back on if that helps. Jason

No worries. Any other clues? Still happening, even after moving the **** DHCP over to the WRT54G. Have you tried any of those open source firmware swaps? Any idea if they're any good? Jason

Gameplay 100%. Nice graphics are, well, *nice*, but one thing I've noticed since I got my 360 is that the majority of the games are the same old games we've been playing since PS1, but with a prettier face. I guess it was cool when PS2/Xbox/GC put the prettier faces on those games, but now I'm just sick of those games. When my 360 (the THIRD freaking one!) gets back from MS's repair center, I'm gonna ebay the POS and use the money for a Wii. Screw Microsoft and Sony, I'm sick of the same old rehashed horses*** with prettier pictures. Jason

Thanks. My switch is indeed a dumb switch, and works just fine for what I need it to do. My server's internal NIC's GW was previously pointed to the WRT54G, (as are all the clients, as defined in the DHCP scope), but with the external IP's default gateway also set I was experiencing horrible connectivity problems even staying connected via RDP. Once I removed the internal gateway those problems disappeared. I tried at first removing the external gateway, but then none of my dev team folks could log into the server, which prevented everyone from having access to files for any of our projects. As reported above, DHCP *does* work from the server to clients over both Wifi and physical ports, but even so I've taken your recommendation and moved DHCP to the WRT54G and disabled it on the server. The one thing I haven't tried (but will tonight when I get home from work) is pointing the WRT54G's default gateway to the internal IP of the WRT54G itself. Are you sure that's a good idea, though? It's currently set to the default gateway for my ISP, since the WRT54G is doing all my routing functions. I'm somewhat worried that it could cause some kind of loop or something, but I dunno. I'll try it and see what the hell happens . I've previous attempted to have the router forward FTP and other requests to the server directly, but that met with minimal success. Ugh. Jason

I want the server and the router on separate IP's for various reasons. Jason

It is consuming *an* IP from my provider, but that's OK, I have four statics. That's the entire reason that there's the switch in between the DSL modem and the WRT54G. Both have external IP's of 66.159.238.xx, each with its own. The internal interface of the WRT54g is 192.168.0.1, since it's the default gateway for all clients, and the server's internal IP address is 192.168.0.102. The clients are on DHCP. In a change from when I originally posted I now allow the WRT54G to do DHCP, but that doesn't seem to be helping at all. Of course I don't have the server naked, though, I've got a firewall on it, and of course I've locked down everything but the needed ports for that interface. Ack. Jason

yeah, as I was putting this together it started to make less sense to me, even, LOL. Somehow it made sense at the time.

Well I've tried my server with default gateways at both interfaces, which Windows tells me is a non-no, but that didn't help either. All my PC's are being given the default gateway of the router itself (192.xxx.xxx.1), since that's the outbound internet connection. I'll see if I can't whip up an illustration, LOL Jason

My wireless strength is *excellent* in every room of the house. I've tried every channel from 1-11 unsuccessfully. I haven't tried my PC with a cable to see if it still happens, but ultimately I want to be wireless regardless so it's kind of immaterial except perhaps for isolation purposes. The logs so far show only "disconnected" and "reconnected". I'll see if I can find something better later on when I get home. Jason

Yeah, I have the router's firewall (NAT) running for network connection sharing purposes. What happens is that offline files loses connectivity, and DFS does at the same time. Manually synchronizing fixes both issues. This doesn't affect internet connectivity at all, nor even my RDP connection from my desktop to the server itself, interestingly enough. It's as though the router doesn't want to do routing for *internal* machines. Any clues would really help. Thanks! Jason

I've been having a problem for awhile now and it's driving me up the wall. I thought it was my cheap Belkin router, so I replaced it with the fabled Linksys WRT54G in hopes that the problem would go away, but it doesn't. Some detail: 2003 Server, Domain Controller (DNS server, DHCP server)-->WRT54G on internal interface (no default gateway, first in Connections list), directly on Internet via second internal interface (default gateway, second NIC in Connections list). WRT54G-->DSL connection on WAN, Server on LAN ports, 2 client PC's via 802.11g Domain User accounts with redirected My Documents (Offline files enabled) Every few minutes at random intervals, I get the "You are no longer connected to [servername]" error message and the system begins working offline. In this condition I cannot access my DFS root. RDP connections work fine and are stable, and if I simply right click the offline files icon and choose "Synchronize" the problem disappears for awhile. The WRT54G is acting solely as my router, there is no DHCP running on it. I have also updated it to the latest firmware (1.00.09, if I recall) which is supposed to resolve an "internal DNS server" issue. My own server reveals no errors in the logs whatsoever, and a DNS check passes instantly every time. Extended logging reveals no errors. Any help would be greatly appreciated, thanks! Jason

Err, I dunno what copy of Perfect Dark Zero you played, but IMHO it looks like *a*** and worse it *plays* like a**. However, the 360 does have some very good games. I've enjoyed my 360, at least what I got to play of it before it kicked the bucket. At least it died in warranty, the replacement should be back soon, I hope Jason

HAHAHAHAHA, that's *hilarious* PS3=Xbox 360+Betamax 2.0 Jason PS3 can't produce better graphics, LOL. It's effectively running a Geforce 7600GT. It's on-par with 360, it's not better. And if RSX has inherited the 7xxx family's inability to perform FSAA and HDR rendering simultaneously, you'll see 360 pull ahead, because it *can* do both. In the long haul, though, I expect both systems to remain on par, though 360 is still a better deal. That said, I'm disappointed in both 360 *and* PS3, which both appear to be home to "more of the same, just prettier". Jason

I don't touch the driver recompression, but I do wonder if it gets kicked off automatically if you remove any of the existing drivers. As for my source, I'm using the same source I've used ever since SP2 first hit, and through numerous versions of nLite, it's only the last version or two that seems to screw it up, I have no idea why. My source started as an RTM and I integrated the SP2 into it the Microsoft way when SP2 first came out. Weird. I wonder if I still have a copy of RTM around here somewhere... Jason

I'll jump in here. I have the same problem. I am using a non-nLite winnt.sif. I also use a non-nLite winnt.sif. Are there any parameters that ought to be enabled/disabled in order for nLite's tweaks to work correctly? Jason

OK, I tested my driver.cab and sp*.cab files and found zero errors. However, what I did note is that post-nLite, there's no SP2.CAB, whereas it was there before. All I removed on that pass were a couple of items in hardware support. any ideas?? Jason Last_Session.ini

So, then what do I do? Just not remove any drivers at all? The only sucky part of that is that there's probably close to 100MB of stuff that I could safely remove if it wouldn't corrupt the driver.cab when recompressing. Any idea why it gets corrupted and if there's something I can do to fix it? thanks Jason

OK, I've narrowed the problem down to nLite's removal of built in XP *Drivers*. I went item by item starting at the top and removed a section, built the ISO, rang through the first part of install, then I'd proceed to remove from the next section. I never once got the error until I removed some of XP's built in Drivers using nLite. Attached is my INI. Anything we can do? Jason Last_Session.ini

Oh, OK, now I understand a bit better On my CD, I slipstreamed SP2 into my XP RTM source manually, using the Microsoft method. Subsequently I used nLite (the first time) to addin all the RyanVM packs and such and remove components, which gave me the error. Then I tried again, using the Integrator to add the RyanVM packs and nLite to add tweaks/remove components, and I got the error. When I used the integrator on my source and *didn't* remove anything or add tweaks, it installed just fine. Of course, I'd prefer it to install fine SANS these silly bloat components, LOL. Jason

Explain please? What's wrong with the disk having already had SP2 slipstreamed into it? nLite supports that scenario just fine and always has as far as I know. I also know that my SP2 slipstreamed disk is fine, it works flawlessly and I've installed hundreds of systems from this source, all problem free. In past versions of nLite I've also made nLited disks from this source, most problem free. I'm not sure I understand what you're saying, I guess. Jason

Well, that's what I did first The only reason I used the integrator at all is because nLite gave me those errors when I tried to use it to install those same updates that worked fine in the later test with the integrator. Jason

My copy of WinXP SP2 corporate was slipstreamed into an RTM corporate copy of XP. I've redone the slipstreaming process just to be sure, but the same thing happens. I agree it's probably a corrupted driver.cab, but could the way nLite recompresses it have something to do with it? When I use the naked RyanVM integrator and don't do any nLiting it works *fine*, so I'm sure it's not the packs nor the integrator. thanks for looking, Nuhi, mucho appreciativo Jason

So I guess nobody knows why this is happening? Jason