allnighte

Member
  • Content Count

    28
  • Joined

  • Last visited

Community Reputation

0 Neutral

About allnighte

  • Rank
    Member
  1. allnighte

    Page File not creating

    i looked in the changes list for SP1, nothing in there about page files at all. and i did a google search for my SCSI card and page file - nothing came up there either. i doubt it's the SCSI card, as it's a pretty popular card and i imagine a lot of people have a page file on a drive on it :s nice suggestions though
  2. allnighte

    Page File not creating

    oops, forgot to mention that in my post yes, I'm running WinXP, non-SP1
  3. allnighte

    Page File not creating

    my setup is as follows: AXP 1800+ 512MB PC133 MSI KT7Turbo2 LSI Logic U160 SCSI card Seagate Cheetah X-15 36LP 18gig (C drive, boot drive) 5400 RPM Maxtor 20gig on IDE (D:, storage) my problem is that windows will NOT make a pagefile on C, no matter what I tell it. I can freely change the size of the page file on D, but if I tell windows I want a 500 MB page file on C, and nothing on D, it will put 500 MB's on D. I've tried changing registry settings manually (even changing the path of the pagefile from root to WINDOWS or even another directory) I've tried setting the local security policy - "create a page file" from Admins to Everyone I've also taken out my D drive, but when windows starts up, it says "no page file exists" and says "a temporary page file has been created" but I don't see any page file. I've googled for a long time and haven't come up with anything that can help. my C drive is a dynamic disk, and I thought that may be the cause, but there is no mention about dynamic disks not having page files on MS's site. I know the computer needs "system" access to the drive to create a page file, but there is no option to set any security settings when I go to the drive/folder properties any ideas?
  4. allnighte

    Western Digital Raptor WD360GD

    all this firmware tweaking makes me wonder what could happen to my X-15 36LP if it was tweaked for single-user performance
  5. allnighte

    10k rpm ata drive from western digital

    did you happen to see the front page of http://www.storagereview.com ? it's a great site, check it out sometime just playin'
  6. With raid0, you get better throughput but equal or worse access time than a single drive. With a 10k rpm drive, you get better access time. It's two different "speed"s you're talking about. I don't think you can improve access time no matter how many drives you're striping via raid0. Actually, quite the opposite. RAID0 lowers accesstime, and the more drives, the more it is lowered. Lestat (who is about to invest in a 15k.3 ) please, enlighten me with this information (preferably with benchmarks and not theoretical assumptions) i have only seen RAID 0 setups have equal or a bit longer access times
  7. well, if there's no limit as to how much data you can cram per square inch, then i don't think we will ever see a move to >7200 RPM i can see that if the general computer community start to see that access times are important, then drive manufacturers might be willing to make the move sooner it's all up to supply and demand though
  8. i have never had it crash it does, however, time out after what seems like a little longer than 2 minutes try waiting a while, and it should pop up with a red error and you can continue
  9. time for benchmarks that prove absolutely nothing! (except maybe one) my system: Athlon XP1800+ MSI Turbo2 KT133A 512MB PC133 RAM WinXP (non-sp1) 5400 RPM IDE 20 (didn't use this at all) LSI U160 single channel X-15 36LP 18gig almost every patch you can think of, to name a few; via latency, 4in1's (not hyperion), lsi aspi driver, raid performance patch, etc etc etc... now for stopwatch tests! yay! BEFORE DANGEROUS XP FILTER BF1942 startup - 18.9 seconds BF1942 single player load map - 21.7 booting XP - 39.8 581MB tar file copy (from C: to C:) - 90 seconds the untaring of the file - 56.0 raring to the final 603MB .bin file - 74 now some bechmarks! one of only any significance: *^ see note at bottom of post ^* AFTER DANGEROUS XP FILTER!!!!: BF1942 startup - 22.6 BF1942 single player load map - 22 booting XP - 44 seconds (then another reboot, 40 seconds) 581MB tar file copy (from C: to C:) - 83 seconds the untaring of the file - 55.0 raring to the final 603MB .bin file - 78 since i only have 1 cheetah, i can't do a file copy from a data source that can write at more than 50MB/s so what's the meaning of this post? well... just to show that there's no real performance increase (at least, for my system) and i even got an error after installing the patch when i closed explorer (it was a management program that crashed or something) so i'll be uninstalling it and keeping my data safe (i didnt even backup any data before doing this, hehe) *^note^* actually, when reviewing some of my older ATTO's, the "before" results are kindof low. as i had done some tweaking with patches and have come up with the 45MB writes/51MB reads like the "after" result i'm not saying cas didn't do anything, because i'm sure he did but i'm hoping i can help prevent any sort of freakout from some uninformed users thinking this patch is the GOLDEN KEY to "fix" everything
  10. Okay i'm sorry if i'm beating a dead horse... but what does this mean about other programs? ie. games? and boot up? is winXP doing things the same/just as fast as win2k? and are the findings about cascopy and windows explorer true also for RAID? maybe i'm just looking for that definitive "yes" or "no" answer from Eugene i <3 Eugene :wink:
  11. allnighte

    Terrible SCSI performance in Windows XP

    DEAR GOD YES well, for my X-15 36LP that is. the access times aren't affected, so everything still feels very snappy and quick compared to my IDE drives
  12. allnighte

    Terrible SCSI performance in Windows XP

    pardon me if i'm mistaken but are you guys referring to the system files that windows uses for the scsi control? it was stated somewhere (not sure if it was here) that winXP protects certain system files, and re/moving or overwriting does nothing as winXP will just put back the original files sorry if i'm off topic
  13. allnighte

    AMI XP Drivers

    i have the LSI U160. they don't give any drivers on their site for it (2k/xp has built in drivers that LSI recommends) however i did get one thing off their site that helped: http://www.lsilogic.com/support/drivers/sc...si/winaspi.html the win ASPI manager bumped up my transfer rates on my X-15 36LP about 5MB/s (suffering from WinXP/SCSI issue) all in all, i think the winXP drivers are fine
  14. allnighte

    via latency patch not effective

    unfortunately, the other drive i have is a 5400 RPM 20 gig IDE so i won't be able to tell actually, if i can find some RAM drive software, i might be able to test that. *googles for a while*
  15. actually, if i understand correctly, the "tag and seek" isn't yet supported. so no one really knows how much it helps just yet (please correct me if i'm wrong)