Jump to content


  • Posts

  • Joined

  • Last visited

  • Donations

    0.00 USD 
  • Country

    United Kingdom

About kof94

  • Birthday 02/16/1981

Contact Methods

  • Website URL

kof94's Achievements



  1. Very long time... happy new year. I can't see the point either, just seams like a waste disk of space if you ask me. It's been a while since I used Ubuntu but I'm sure there's meta-packages to add/remove the various DE's: # apt-get install ubuntu-desktop I spend most of my time playing with Linux these days (I'll be a SysAdmin one day ) but I'm still making multi-boot disks now and again... I'm just using my USB stick more now. I'm kinda hooked on grub4dos at the moment, it's not as attractive as syslinux but what it lacks in aesthetic appeal it makes up for in features. I just wish they'd add more of the features from Super Grub Disk (USB Shift etc). Is this a remastered Kubuntu livecd?
  2. Nevermind. I realised this does work (what I originally tried) I just needed to create my partition on sector 95 (really helps when you read ). # dd if=/dev/sdb of=MYMBR96.TMP count=96 bs=512 More over, since I can write directly to the device don't have to write create little images anyway (again reading really helps here ).
  3. I'm planning to write a shell script to setup a bootable UFD and I want to add an option to create a triple MBR. From the GRUB4DOS readme I understand I can use this to add a partition boot record (see Note 2 under "Use bootlace.com to install partition boot record"): Assumes /dev/sdb is my UFD # ./bootlace.com --floppy=0 /dev/sdb1 I'm stuck, however, on grabbing the first 96 sectors from the device. I'm very familiar with dd but mind melts when I try to work out how many bytes I need etc. Here's my output from fdisk: # fdisk -l -u /dev/sdb Disk /dev/sdb: 4009 MB, 4009754624 bytes 124 heads, 62 sectors/track, 1018 cylinders, total 7831552 sectors Units = sectors of 1 * 512 = 512 bytes Disk identifier: 0x00000000 Device Boot Start End Blocks Id System /dev/sdb1 * 62 7826383 3913161 c W95 FAT32 (LBA) If someone could please explain how to work this out I'd greatly appreciate it (cue jaclaz ).
  4. Just a thought... If you have a fast internet connection why don't you just do a netinstall and download the desktop you want instead of filling your disk with three squashfs images containing similar files.
  5. I recall something similar, will test again with a few sources and get back. Thanks. I just lauched it manually from a seperate terminal and to be honest I don't thing I've ever seen it run in the entire fours years I've used the DriverPacks. I have a feeling it might have something to do with the start command but I have know idea how to work around that. Encase anyone is interested... I got a response over at DriverPacks.net on this issue. It's only supposed to be used with the defunct KTD function so this error can be ignored.
  6. No, no, no... *instead* of copying to usb stick i.e. do all the modifying of the source and creating the iso but not copying it to the usb stick. I have my reasons, may be others will find it redundant but if you do this many times (testing etc) then a program like rsync would do the copying alot quicker by only copying (or removing) files that have changed. This will also reduce disk wear. Make sense? Ah, fair enough... well 32bit XP works fine It should hide as soon as I start using the regular fake setup.exe, not the debug version which shows the cmd window. Currently, for troubleshooting, as at that stage the troubles are expected, the debug version is used. setup.cmd is hidden by fake setup.exe but you still see the presetup.cmd because it's called by setup.cmd. You'd need something like hidec, cmdow or pistart to hide presetup.cmd as well. I recall something similar, will test again with a few sources and get back. Thanks. I just lauched it manually from a seperate terminal and to be honest I don't thing I've ever seen it run in the entire fours years I've used the DriverPacks. I have a feeling it might have something to do with the start command but I have know idea how to work around that.
  7. Fair enough, I'm not a coder but an option that modifies the source instead of copying it first would be preferred by me. Besides rsync works alot better than copying the whole tree over and over again This is the whole reason way I switched from using cdob's RAM method. I'm already using it and works like a charm Off topic... I added this to setup.cmd to hide the presetup.cmd terminal window: :: +=======================================================+ :: | DriverPacks method 2 http://driverpacks.net/ | :: |-------------------------------------------------------| ::if exist presetup.cmd ( ::echo call presetup.cmd >>winsetup.log ::start "" /wait /min presetup.cmd ::echo end presetup.cmd >>winsetup.log ::) for /f "tokens=1 delims=: " %%? in ('mountvol.exe ^|find ":\"') do ( dir %%?:\OEM > nul 2>&1 && set disk=%%?: ) if defined disk ( start /wait /realtime /separate "" %disk%\OEM\bin\un7zip.exe %disk%\OEM\DP*.7z %systemdrive%\ %disk%\OEM\bin\un7zip.exe %disk%\OEM\bin\*.7z %systemdrive%\ copy /y %disk%\OEM\bin\DPsFnshr.ini %systemdrive%\ if exist %disk%\OEM\*.ins copy /y %disk%\OEM\*.ins %systemdrive%\ %disk%\OEM\bin\DevPath.exe %systemdrive%\D start %systemdrive%\DSPdsblr.exe ) I noticed that DSPdsbler.exe wont run, I get an error that it's not executable (Since when did Windows XP have an executable attribute ) . The commands and paths are identical to presetup.cmd from the DriverPacks so I'm starting to wonder if it's ever worked... especially since I have driver signing disabled in my winnt.sif anyway. Any thoughts?
  8. At T-13 the UFD is still seen as D: but after the second reboot (after oobe, when RunOnceEx is started) it is seen as H: (I have card readers and other disks). It's no problem though I've just switched to using GUIRunOnce instead. Whats new, did you considered this: Also, would you consider changing this: setup.cmd SET TAGFILE=\WINSETUP FOR %%h IN (U C D E F G H I J K L M N O P Q R S T V W X Y) DO ( IF EXIST "%%h:%TAGFILE%" ( SET CDDRIVE=%%h: goto :CDDRIVE_found ) ) to this: set TAGFILE=\WINSETUP for /f "tokens=1 delims=: " %%? in ('mountvol.exe ^|find ":\"') do ( dir %%?:%TAGFILE% > nul 2>&1 && set CDDRIVE=%%?: ) if defined CDDRIVE goto :CDDRIVE_found Stops "no disk" errors for us poor fools with card readers!
  9. Something else I've just discovered... $OEM$ dir works. I don't know why I thought it wouldn't but my cmdlines.txt is ran at T-13. The only draw back is the drive letter for the UFD changes after second reboot so any paths set at T-13 for RunOnceEx are incorrect when you get to the desktop. This isn't an issue though as I can work around it. Infact I could just launch the same script via GUIRunOnce instead and make the $OEM$ dir redundant
  10. If you hit Enter you should be able to delete/create a new partition on your HDD and install Windows. Setup wont allow you to delete the partition on your UFD. If the wrong drive letter is assigned (e.g. your HDD has no partition(s) to start with) then setup.cmd will force a reboot and reset the drive letter to C: at first GUI. I hope this makes sense because I'm a little confused with what your trying to do... do you want to install Windows on your HDD from your UFD?
  11. At the bottom of menu.lst or winsetup.lst (I can't remember) change the line that reads root (hd0,F:) to root (hd0,0) or even better find --set-root /winsetup.lst. This should solve your problem. Edit: Here's some files for you. txtsetup.sif (for ISO), setup.cmd, menu.lst and winsetup.lst files.7z
  12. To be honest so many things could be different with my setup. My main OS is Slackware, I used fdisk (coreutils) to create a FAT32 (LBA) partition and mkdosfs to create a FAT32 filesystem on my disk then ran your GUI inside VirtualBox to do the rest. It's an odd arrangement I will admit but it works for me. Edit: I nearly forgot... The feature I'd most like to see is an option that just creates the ISO without doing the file copying. I can copy/move setup.cmd and setup(org).exe myself! I also did a test removing migrate.inf... it made no difference. @Arvi I had to edit setup.cmd and txtsetup.sif (inside the ISO) to get this to work... I don't know if this helps.
  13. Second go, same thing: File \WIN_SETUP\XP_Pro_SP3\I386\biosinfo.inf could not be loaded The error code is 18 ... The file exists... any ideas? Edit: Nevermind, I renamed the directories \WINSETUP\XP\ and everything works.
  14. Welll my first attempt ended with a code 18 error about missing biosinfo,inf, which *is* on the UFD. I'm gonna give it another go but I have one question... is the migrate.inf really required? The reason I ask is, I create backups of my disk using dd (there's a lot of other stuff on it), if I write my image to a new disk (if say my current disk dies) will it still work?
  15. Well I've certainly learnt something today, thanks to both of you . Edit: I liked both solutions so much I thought I'd combine them: set tagfile=\OEM for /f "tokens=1 delims=: " %%? in ('mountvol.exe ^|find ":\"') do ( dir %%?:%tagfile% >nul 2>&1 && set CDDRIVE=%%?: ) if not defined CDDRIVE ( goto EOF )

  • Create New...