Jump to content

LiquidSage

Member
  • Posts

    575
  • Joined

  • Last visited

  • Donations

    0.00 USD 
  • Country

    United States

Posts posted by LiquidSage

  1. Some extra things tot try/check...

    In BIOS, set everything to a default value (esp. RAM timings) if you OC.

    2.In BIOS, try disabling APIC support.

    3. If you have more than 1 OS (more so if that OS is a linux build) the partition structure might cause the hang.

    4. SMART enabled in the BIOS can cause certain HD's to hang.

    5. Check that all hardware is seated properly and check that the HD is set to Master...not Cable Select.

    6. If you added custom drivers through nlite or other means......

    The drivers may not be getting along with your hardware. Try F6....

    Winnt.sif may have values that have been known to break driver installation and initialization of setup if certain prerequisites are not valid in your sif.

  2. don't forget, when somethings not right... do a virus and more importantly in this case, a spyware/adware scan. Check the startup entries, more than likely you will find the culprit there.

  3. Zxian has a point...

    Putting the swap in the middle of the disk (and/or it's own partition) will lead to reduced performance. Since the OS on C:\ tends to put a lot of critical and frequently used files at the beginning, every time swap space is used, the disk will have to access the middle, and then get back to the active partition. If swap is on C:\, the distance is much shorter which ='s less access time.

    There have been posted benchmarks for I/O performance and guides for swap, but the general view is that the system really does know what it is doing when it comes to swap. Just let it govern itself. Setting the size too large can set you up for swap fragmentation, setting it too small will lead to out of memory' and heavy I/O activity on disk

    Since the swap size needed is based on your activities on the PC, someone who plays games, uses graphic programs, sound/video editing will never have a set swap size that will be perfect as the swap shrinks and grows depending on your use.

    If you have 2 disks, setting a smaller swap on C:\ and then let windows determine swap size on the other disk seems to show good performance for multi tasking. Performance-wise the boost is marginal, while a incorrectly configured swap can lead to a serious performance hit.

    Windows will always want some swap space on the active partition, so it is best always leave something for it. Never move it entirely.

    What has shown good performance, is setting a small swap on C:\ and then put more swap on a RAM disk. The draw back is you need to get more ram for your system and resist the urge to set the RAM disk size too high.

    Also, with a RAM based swap, privacy concerns are minimized since it will clear itself upon shutdown.

    FYI - Programs like Photoshop would benefit more if you make a Ram disk and instead of letting windows use it for swap, you tell the program in it's options to use the RAM disk as it's temp space

  4. Virtual CD's are require the installation of a driver, otherwise the virtual hardware can't exist. You can install silently with some....with all you can repackage the setup using a install-capture program. Then change the settings to your liking and create your own setup.

    There are programs (like BTEWin and DaemonScript) that make automated scripting of mount/unmount,run program/open files etc. possible as wel.

  5. seriously, the links given should be enough. Your questions have all been answered, including adding floppies. The thing is you have to read and digest the info. No one can give you a set directory structure because everyone has different things on their multiboot and/or unique naming styles.

    You want to boot and setup 95-98 /ME.......read up at tech-hints about 95/98. It explains

    1.How to get and prepare bootfiles.

    2. What type of files you need to install an OS.

    3. How to go about naming the OS folders and how to direct the bootable image towards it.

    3. How to automate setup and integrate the cd-key.

    You need to read......read......gather resources.... read....test....then post saying you have tried everything.

    I suggest you begin with the The 911 Rescue CD so you can get direct links to some bootable images needed and you can see how to put them in it's structure step by step. Then read some more and Search the forums. Everything you asked and wanted has been answered and given.

  6. you mentioned using cdshw.com. You should know that when testing your ini file using cdshw.com, no actual cmds are performed. (Just imagine if you were testing your menu and you hit an option for some kind of auto-disk erase boot disk....) Your error is most likely this. (I dbl checked with a script of mine and I got the same error as well).

    Actual testing must be done booting.

    If this isn't it, then you probably don't have a complete set of files in the 'modules' folder.

    Just to make sure you are aware of the process.....

    -You must set the boot file to loader.bin in the boot folder.

    Loader.bin will trigger cdshell.bin which will start your cdshell.ini menu.

    --When booting using memdisk or diskemu...Some mobo's will give you an error if you have disabled your Floppy disk controller and/or selected None for Drive A's type in BIOS.

    --Be careful mixing cdshell and bcdw. You need to be aware of version incompatibilities (PM me if you want a copy of both that work together. -CDShell 2.0.11 and bcdw 1.5z plugin-)

    Regarding paths....

    -To start from the root dir. use "/" first. Ex. /boot.ima <---this makes for a messy root

    -Relative dir starts with the folder name then "/".

    I personally create a folder in boot called "files" and use /boot/files/xxx.xxx

  7. Well....if you pay the extra $1 or so a month for the phone maitenece fee,you could gunk up your wall jack with some dirt or a bit of juice or something not too obvious.....then complain to the phone CO. and when a tech gets out there....tell him that the internet is really bad in general as well. Ask him to install an addiotional jack next to your computer. He will either do that or change your wall jack to one with 2 connections.

  8. if nero's msi needs setup.exe to run....

    1. You will need to add ISSETUPDRIVEN with a value of 1 to the property table

    2. Go to the Custom Action table and put a condition in with the editor "OnCheckSilentInstall" that will come out always false or delete all the condition checks entirely.

    ---Best practices would suggest that you make these changes and save them as a transform (.mst), not directly to the .msi itself.

    You will still need to install isscript before installing nero or capture the installation and repackage it (which might end up being a little easier).

  9. If you are getting booted because of connection, there is nothing you can do. On slow connects your upload gives location and response time less frequently, so much so that servers may just kick you out to let someone else who can actually keep up have your slot.

    Basically, unless you are hosting or ask the admin to reserve your spot, you out of luck. Today's online games (even RPG) really can't be played w/o a broadband connection.

    I'm surprised you actually play on a modem, the lag alone would be enough to start me pulling my hair out. :realmad:

    Assuming you don't have MS Auto Updates, Firewall, Antivirus/Spam blockers and anything else running while playing... about the only thing you can do is...

    -Make sure the phone cord you use is good quality and as short as possible.

    -Connect the modem directly to the wall phone jack. Try not to put it on a splitter and make sure the wal and modem connections are clean. If not a alcohol swab can be used to get the grim out.

    -If you live in an apt. building....I've heard of people jumping on other people's wi-fi connection and running undetected since the avg. user never looks at their router config pass the initial setup....It may just be a rumor though.... :whistle:

  10. get a print server....wired can be found for as little as $20-$30. The wifi is more expensive, but if you get one that matches the brand of your router (if you have one) it is a painless install. If you don't have a router, consider getting one with a built in print server.

    Linksys -http://www.linksys.com/servlet/Satellite?childpagename=US%2FLayout&packedargs=c%3DL_Product_C2%26cid%3D1114037289336&pagename=Linksys%2FCommon%2FVisitorWrapper

    http://www.epinions.com/Print_Servers--rev...ice_range_0_100

  11. sorry..few corrections....

    1.it's 6 disks, not 4.

    2. All files must be in a folde I386 and ident files must be at root....win51win51ip...etc you must make sure the boot file (2k in size) is poiinting to I386.

    graphic examples can be found at the multiboot guide. Just follow it up to maKing a boot folder for an os install....after that you have it.

  12. hp 7310. It has network support. Never has jammed,never had a prob

    It gets used to death for work. I must have filled the SAME cartridge about 15 times so far and it has yet to complain. Also, HP finally released a package w/ Drivers & network support. Before you almost had to install the whole 500+ install package for it to detect and find the printer. :puke:

    Almost all HP AIO are either network ready or can be w/ the network add-on option.

    I have used the 5500 series which is cheaper and it is very nice as well.

    I may be biased, but HP has the best AIO's IMO. HP printers have always been soliid, though i think Lexmark has better super hi-res quality.

  13. -Is he overclocking his chip?

    -Get the latest BIOS update! (I have an ECS board that rebooted often, ECS had a problem w/ HT CPU's and chips over 3ghz. My board works fine now)

    -Check the rail voltage in BIOS . You may need to set cpu and ram values a bit higher so they don't drop too low. (2-6% should be enough.)

    -Make sure you don't have the memory timing too tight. Usually making sure that CAS is set by the mobo and that it is at 2T and not in Turbo mode should provide stability.

    -ECS mainly use VIA chips and though a lot of factors contribute to BSOD's, it seems VIA enjoy crashing more than others.

    -Disable in BIOS, everything not used (Serial Ports, Onboard RAID if not using a SATA HD, modem, etc)

    -I'm sure as this thread builds in size, you friend can read it and convince himself to get a better board (Abit, MSI, ASUS etc)

  14. There is a utility made by a msfn member that can trigger a recovery cons. install....after that replace the appropriate boot files and it will work as a standalone bootable image.

    You can take the four disk set, and either.......

    1.Open the first disk in winimage. Then goto Image--> change format--->select custom format--->change Total # of sectors to ~16000. After that extract the 3 disk into a folder on your computer.Drag and drop those files into your new 8meg image and save.

    2. Extract the boot sector from an xp cd and put all files from all 4 disks in a folder named i386. save ISO and burn for stand alone recovery console..

    Or since RecCons is basically made of the same files from a OS's boot folder. Follow the guide here on MSFN and create a bootfolder, call it in cdshell. (You can stop there and not go on to connect the boot files to an OS installation folder if you so choose.

  15. Bliss on the cd would be BLISS.JP_ and so on.

    Search your cd's I386 folder using --> *.JP_

    Then sort the results by size and you will see just about all the wallpapers.

    Easiest thing to do is to grab all the wallpaper jpg's you want to use and name them the same as a windows wallpaper file. Then cab them and change the extension to .JP_. Replace the deafult file in I386 and you are done.

    Do a search on msfn for a menu add on that will cab the file, apply modifype and rename it for you to .xx_.

    I think the download link was called "CAB Tools for SendTo folder".

    If you want to go with your 2nd suggestion, just be sure to send the wallpaper to

    the WINDOWS\Web\Wallpaper folder.

  16. It's the same process....make the PE ISO.....extract all files to a folder ROOT.

    Modify the boot file (xxx.dat) to point to a 4 character directory that was once your PE's I386 folder (lets call it XPPE). Now edit XPPE/setupldr.bin, changing all occurances of i386 to XPPE wiith a Hex editor.

    Now add everything else making sure all folders/files that were at root are copied in like fashion.

    Personally... I make the OS boot folder names unique so all I have to do is just put a PE build in w/o changing a thing. Heres how my directory looks.....

    ROOT

    ---XP01 Boot folder for XPInstall

    ---XP02 Boot folder for XPInstall

    ---I386 BartPE

    ---PROGRAMS Used by the PE

    ---Documents and Settings Used by the PE

    ---BOOT CDShell

    -----CDshell folders,etc

    -----Files I keep boot files in here

    -----XP I keep XP Builds here

    -------XP01 XP Install

    -------XP02 XP Install

    Don't forget the files that must stay at root (win51's , for PE include winbom.ini)

    If you use ReatoGo or a different type of PE, you may or may not have D&S, PROGRAMS folders. Just remember the dir. structure mst be the same when you add it to a multiboot distro.

×
×
  • Create New...