Jump to content
Strawberry Orange Banana Lime Leaf Slate Sky Blueberry Grape Watermelon Chocolate Marble
Strawberry Orange Banana Lime Leaf Slate Sky Blueberry Grape Watermelon Chocolate Marble

MSFN is made available via donations, subscriptions and advertising revenue. The use of ad-blocking software hurts the site. Please disable ad-blocking software or set an exception for MSFN. Alternatively, register and become a site sponsor/subscriber and ads will be disabled automatically. 


  • Content count

  • Donations

  • Joined

  • Last visited

Community Reputation

0 Neutral

About tosk

  • Birthday 06/15/1985

Contact Methods

  • MSN
  • Website URL
  1. Multi-Processor Support...

    It should mean 4 physical sockets are supported, not cores.
  2. Install 98 Without CD

    I've done this before. The 98 CD contents were shared from a Windows 2000 machine to the local network. I got a DOS boot disk, the DOS drivers for the ethernet chipset and the Microsoft LANMAN software for DOS. Just booted off the floppy, prepped the drive, started LANMAN and copied the 98 CD contents to a directory on the blank drive. After that, I shut down LANMAN and ran setup. It can certainly be done.
  3. Where to buy laptops online?

    I recommend Newegg.
  4. XP64 vs XP32 vs Vista64 vs Vista32

    Well, it all depends on the hardware really. There isn't too much support for XP64 as far as drivers are concerned. But their might be drivers for your laptop for it, so definitely check before deciding. I used to run XP32 and denounce Vista. But really, Vista isn't so bad if you have the hardware to support it. All of Vista's annoyances can be turned off. Between 32 and 64-bit Vista, I would say go 64-bit. I've not run into any problems with application compatibility and the driver support for Vista64 is pretty decent. Also, as mentioned above, since you have 4 GB of RAM, you should think about going 64-bit. That way you can use all 4 GBs of it. I personally think Vista64 is better performance-wise than Vista32. YMMV of course.
  5. Can't install in AHCI mode

    I had this same issue with Vista 64. When it asks for the drivers, give it the 64-bit ones first. It'll then display the error about signed drivers. Just click OK and go back to the disk selection screen. Once there, install the 32-bit drivers for the device. It'll give you another warning about signed drivers. Again, ignore and continue. Once back at the disk selection screen, your drive(s) should show up. Proceed with installation normally. When I do this, the 32-bit drivers I select allow setup to see and use the disk for the purposes of copying the files. However, when it reboots, it boots into 64-bit and uses the 64-bit drivers I selected.
  6. sp1, where r u!?

    Just install vLite. Once it's installed, and you have downloaded but not run the SP1 service executable, open vLite and when it asks for the file to slipstream into the source, give it the service executable. vLite will automatically extract it's contents and perform the slipstream for you. See here for more information: http://www.msfn.org/board/Tutorial-Build-W...-D-t114957.html
  7. Nestopia

    I'm quite fond of Nestopia's 'Export to AVI' function myself.
  8. UTP cables

    Splicing cables is also not "up-to-code." In an environment where you would most likely be installing UTP (ie-not a private residence), you would need to make sure that all wiring and cable runs meet industry standards at the time you perform the installation. I think that joining small segments of cable together as shown in Exhibit B would even be acceptable to code regulations. I know for sure though that Exhibit C would not only get you fired, but possibly fined at the same time.
  9. *bump* Fixed the download link. It's available again as requested.
  10. Is this documented anywhere and is it freely available? Or do you know what's required to actually do something like this? Also, is it possible to make the call using rundll32? Through some trial and error, I've found that using AddFontResource doesn't work. It has to be called as AddFontResourceA and even then, it doesn't add the appropriate entries to the registry. I'm sure I've just not done something right and that's why it's not working. Any help would be greatly appreciated.
  11. Is this documented anywhere and is it freely available? Or do you know what's required to actually do something like this? Also, is it possible to make the call using rundll32?
  12. Yah. I knew you could do that. But doing that you actually have to open Fonts to register them. To me, that kind of defeats the purpose of an unattended install since the fonts aren't actually installed until after setup finishes, the system boots for the first time and the end-user has control. Besides, I was incredibly bored this weekend and needed a way to kill some time. This is also a small proof-of-concept for a project I'm working on that requires a registry access API in Java. I'm going to test running it from [setupParams] in WINNT.SIF after I add the ability to specify the font directory as an argument.
  13. EDIT: Modified code to allow user to specify directory containing fonts. I wrote a small utility that can aid in installing fonts during a unattended installation. The utility is silent, in that, it has no display or interface. It will run silently in the background and do it's work then exit. It has only one argument. If the user wishes (it's preferred) the directory containing the fonts to be installed can be specified as the one argument. If no argument is given, it uses the working directory. How it works First, it gets a list of all the files in the working/specified directory, then it processes all the ones that have the .ttf (.TTF) extension. After it gets it's list, it copies each of the files to %SYSTEMROOT%\Fonts and creates registry entries for each of the fonts. Unfortunately, I don't know of any available API for Java that can parse a TTF and retrieve the font name, so the entries in the registry are labeled "System Installed Font (# ?)" where ? is the number that font was processed. After a reboot the fonts are all available with their proper names. So you won't have to worry about opening Word and seeing "System Installed Font (# 12)" in the font selector. The utility depends on the presence of the REG.EXE tool. If this tool doesn't exist or isn't in your path, the program will fail but will not display any errors. How to make it work The whole purpose behind using this tool is so that when the system boots for the first time, the fonts are available without user interaction. So the tool will need to be run during GUI-mode or during RunOnceEx if your setup automatically reboots at the end. Remember: the system must be rebooted before the fonts will appear. That's why it's best to do it during GUI-mode. The best way (according to me) is to run it during [setupParams] in WINNT.SIF. Here's an example using [setupParams] in WINNT.SIF ... [SetupParams] UserExecute="%SYSTEMDRIVE%\Fonts\typer.exe %SYSTEMDRIVE%\Fonts" ... Here's an example using cmdlines.txt: D:\ (ROOT OF CD) -$OEM$ -$$ -$1 -Fonts -FONT1.TTF -FONT2.TTF -another.ttf -... -typer.exe -cmdlines.txt -fonts.cmd cmdlines.txt [COMMANDS] ... "fonts.cmd" ... fonts.cmd %SYSTEMROOT%\SYSTEM\CMDOW @ /HID @echo off %SYSTEMDRIVE% cd Fonts start /wait typer.exe exit That's one way to do it. I'm experimenting with different ways to clean it up so it's completely silent and the end-user is oblivious to what's going on. The utility was written in Java, but was compiled to native code using GCJ and packed using UPX. Below is a link to a zipped copy of the native binary. Source is included and will successfully compile and run with Sun Java 1.5 (bytecode) and GNU GCJ 3.4.0 (native and bytecode). License: You may use this utility as you see fit and may use it's source as you see fit. This utility has NO warranty. I have tested it and it works fine for me, but don't blame me if you use it and it destroys the world. Note: I've tested it on already-installed systems and on my unattended CD. Both times, the utility performed appropriately. Download: typer.zip Size: 1.26 MB (1,292 KB)
  14. Jumper your existing drive (in the working machine) as the master and the one from the busted machine as slave, then connect both to the primary IDE channel.
  15. I did a search and couldn't find anything relevant to my situation (or at least what I thought was relevant). I made an "unattended" XP SP2 CD. It isn't a fully unattended install. All it does is simplify the installation process by providing answers for most of the setup screens by using WINNT.SIF. My problem is that upon first boot of XP AFTER the install, I get the Welcome screens and then the Administrator account tries to auto-logon. I do not want this to happen. I want the user account I create in the Welcome screens to auto-logon. However, this only happens if I actually supply an Administrator password during install. If I leave the fields blank, it will auto-logon like normal with the created account. My non-unattended SP1 CD will auto-logon with the created account regardless of whether there is an admin password or not. This is how I want my SP2 CD to behave. Below is my WINNT.SIF and CMDLINES.TXT. Thanks. WINNT.SIF: ;SetupMgrTag [Data] AutoPartition=0 MsDosInitiated=0 UnattendedInstall=Yes [Unattended] UnattendMode=DefaultHide OemPreinstall=Yes TargetPath=\WINDOWS OemSkipEula=Yes DriverSigningPolicy=Ignore WaitForReboot=No [GuiUnattended] AdminPassword="" AutoLogon=No EncryptedAdminPassword=No OEMSkipRegional=1 OEMSkipWelcome=1 TimeZone=20 [UserData] ProductKey=XXXXX-XXXXX-XXXXX-XXXXX-XXXXX [Identification] JoinWorkgroup=WORKGROUP [Networking] InstallDefaultComponents=Yes [TapiLocation] CountryCode=1 Dialing=Tone [Components] msnexplr=Off CMDLINES.TXT: [COMMANDS] "RunOnceEx.cmd" RunOnceEx.cmd: Note: REGPATCH.REG does nothing with the auto-logon settings in the registry. cmdow @ /HID @echo off REGEDIT /S %systemdrive%\InstExtras\regpatch.reg EXIT