wildguy2k

finally got a machine up & running yesterday. thing is, now every time i boot up, the pagefile has disappeared. i get the, "your paging file is too small, & a temp one has been created" error msg every time. then, every time, i go & fix the problem, & the pagefiles are created (1 per partition). i check to see that they're all there, & reboot, & the same prob happens again. i've done the emergency repair console to no avail. i'm thinking this is a hware problem? anyone seen this before & fixed it (w/out re-install)? this is sp2. after installation of all my apps/drivers, i defragged each of the fragmented partitions: c:\ system & drivers only d:\ applications e:\ storage each partition (supposedly) has a 384-768 pagefile. this is a ecs k7s5a board w/an xp1600, 256mb crucial ddr, & a 40gb 60gxp.

I have a Netgear FA311, & I'm trying to make a DOS bootdisk via the Ghost bootdisk wizard, & also manually. I have used both versions of the FA311 driver (1.30 & 1.80) in both methods. When using the Ghost wizard, I have used the default NDIS2 driver, & I have also created a new template using the WFW311 directory driver as per the Netgear support page. I have also disabled PnP in the BIOS. Both of these drivers, from both versions, have returned the same error code under IBM NetBind 2.1: "Warning: Since the MAC driver doesn't support loopback, the NTSNX driver may be necessary. Bind or open adapter request to MAC driver failed: error 5707." Furthermore, I have attempted to manually create a DOS network bootdisk using NetBEUI as my protocol. However, using both driver versions (1.30 & 1.80), the same error is returned: "IPX or NetBIOS must be running for net services to start." Does this mean that the FA311 NDIS2 driver isn't capable of passing the NetBEUI protocol? Any help would be greatly appreciated.

well, i just installed the newest version of ghost (was using 7.0, now have 7.5), which has an option to use MS DOS instead of IBM DOS to make the bootdisks. however, it requires the MS DOS network client files, & i don't have an NT server cd here. i d/l'ed a zip of the m$ client files & put everything together, & made a bootdisk of it all, but the machine wouldn't boot. it just sat there @ the prompt for the boot order, churning away on the floppy drive. i think that the copy of the client files that i d/l'ed is either incomplete or corrupt. either way, i know it was the floppy, b/c i replaced the disk w/a disk made w/the IBM DOS from the 7.5 ghost, & got the same error msg..... (but it DID boot).

just tried the beta driver w/no success. ;( any other suggestions?

DS3 yes, i have tried everything in your reply EXCEPT for the beta driver. didn't find that one on my 1st inspection. gonna try that now & see what happens. thanks for your reply.

is this just the entire program w/all the bundled fixes to date, or are there changes to the app itself as well?

uhhhhh, that link is for winxp sp1...

i've just re-built my win2k domain after a dc crash, & the "domain users" group is unable to logon to any of my wkstns. they're getting eventid: 533 - your user acct is not configured to allow you to use this computer, please find another. so, i checked my domain security policy, under user rights assignment to see if the correct setting was made. the following appears under the "logon locally" setting: Administrators NAME\Domain Admins NAME\Domain Users SYSTEM SERVICE (**NAME, being the domain name) so, i checked their individual user accts under the "account" tab to make sure that the default setting under the "logon to" button was still set to "all computers," which it was. then i checked the individual wkstns to make sure that the domain policy was being applied. both Domain Admins & Domain Users were found under each wkstn's "logon locally" setting under their Local Security Policy. i then enabled NetBT on each of the wkstns, to see if that would help, but it didn't. in addtion to support.microsoft, & microsoft.com/technet searches, i've run a forum search & found this post: http://www.ntcompatible.com/vb/showthread.php?s=&threadid=18209&highlight=event+533 unfortunately, it did not shed any light on my situation, however, it seemed that his problem was solved by manipulating this "logon locally" setting. however, the setting that he said he switched seems to be correctly applied in my case. i haven't applied any secuity templates, & the "logon locally" setting is one of only a few domain user rights assignment policies that i've defined. IPSec is not running, nor are any IIS or terminal services. ONE VERY STRANGE THING: ALL users can logon to my sole DC. only the wkstns are giving me this problem. i also checked for differences between my domain security policy, & my domain controller security policy, & could find no glaring differences. i'm tempted to "undefine" the "logon locally" user right assignment altogether, but would like some security in the domain. PLEASE HELP

also wanted to add that both wkstns are fresh builds as well, & have been added to the domain following its rebuild. additionally, i can (as a domain admin) logon to all machines, w/full access to all domain resources.

the "IRQ Not Less Or Equal" is most certainly a device driver issue. if you go into your device mgr, under view, set it to view "resources by connection." once you do this, check out the I/O, & Memory (most probably the memory, as the hex values you're seeing are most probably memory addresses) drop down menu's until you find the code that equals what you're getting during the error/BSOD's. once you find it, you'll know which device is causing the problem. change out those drivers & see what happens. (i'm assuming that the error codes you're getting w/the "IRQ Not Less Or Equal" are identical, or nearly so) happened to me using beta detronators once before

i'm still getting the, "your paging file is too small, & a temporary one has been created" error message every time. then, every time, i go & fix the problem, & the pagefile is created. i check to see that they're all there, & reboot, & the same problem happens again. the values for the pagefile are still displayed both in the "performance options" window, & in the registry key: HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Control\SessionManager|MemoryManagement|\PagingFiles it seems that windows will simply not read them. this is windows 2000 service pack 2. this problem happened on my initial install, & i have since re-installed windows 2000 two more times with the same result. all memory timings are set to default, & all drivers and the bios are the updated versions. on my latest installation, no problems occurred until after i ran the sisoft sandra drive benchmark. this is probably because it was the first time since the installation that the entire pagefile was used. i have tried placing the memory in both memory slots & using 2 different sticks of memory. one 128MB, one 256MB, both DDR, both crucial RAM. i have tried other venues for obtaining help, to no avail. see the thread on this forum that i started: http://www.amdmb.com/vb/showthread.php?threadid=101880

wasn't sure which forum to post to....

finally got a machine up & running yesterday. thing is, now every time i boot up, the pagefile has disappeared. i get the, "your paging file is too small, & a temp one has been created" error msg every time. then, every time, i go & fix the problem, & the pagefiles are created (1 per partition). i check to see that they're all there, & reboot, & the same prob happens again. i've done the emergency repair console to no avail. i'm thinking this is a hware problem? anyone seen this before & fixed it (w/out re-install)?

sorry, this is sp2. after installation of all my apps/drivers, i defragged each of the fragmented partitions: c:\ system & drivers only d:\ applications e:\ storage each partition (supposedly) has a 384-768 pagefile. this is a ecs k7s5a board w/an xp1600, 256mb crucial ddr, & a 40gb 60gxp.

i'm using one win2k server machine for my dns, dhcp, & ad. this machine has a pci modem which i use to dial-up to the internet. upon enabling ics, my ip is set to 192.168.0.1, & i have configured my dhcp scope accordingly. the current scope options are pointing the "router" (default gateway) option to 192.168.0.1, pointing the "dns server" option to the same ip, & defining my domain name. on-demand dialing is enabled for ics & my dialup connection is configured for dhcp. as it is merely a home lan, & i am not constantly connected to the internet, i have not registered my domain. dns is configured with one fwd & one rev lookup zone. they are both ad integrated, & the server is a root server, which doesn't allow me to enter forward'ers or root hints thru the gui. a check with ipconfig & nslookup both confirm that all options that i have currently enabled are working. pinging back & forth across the network is possible & both files & printers are successfully shared. the problem is that attempting to access the internet via a win2k client machine will always bring up error msg's. no outside internet content is available to any machine on the network besides the server; however, pinging my isp's dns server (or any other internet ip) from the client machine is possible. the only reason i've setup dns on my server is because it is "recommended" for best ad performance. previously, under a different installation (w/out dns), internet content was served to the entire network (which consists of not only win2k, but win98, linux & unix machines) without problems. have tried adding the ip address of one of my isp's dns servers to my dhcp scope options & configuring dns to note that server as a 2ndary server for the zone; with no luck. any help would be appreciated.