115 reputation
5
bio website
location Earth
age
visits member for 1 year, 5 months
seen Jan 19 at 16:01

Appipulai!

"The aim of an argument or discussion should not be victory, but progress" - Joseph Joubert

"I don't know the percentage of the Internet that's valid, do you? Jesus, it's scary" - Hunter S. Thompson

May The Source Be With You!


Nov
11
revised All FireFTP passwords gone after auto-update
added 12 characters in body
Nov
8
accepted All FireFTP passwords gone after auto-update
Nov
8
comment All FireFTP passwords gone after auto-update
This is just absurd: three day's ago I verified (and re-set, just to be sure) that "app.update.enabled" and "app.update.auto" are both set to "false". Yet, just minutes ago, Firefox updated yet another add-on.. (and the settings you referred to, are still set to "false"). Why?
Nov
7
comment pxe boot dos 7.x / 8.x on modern mainboard without floppy controller
@MichaelKjörling: Set what things through config.sys? @ Pat: as far as can currently tell, just removing the "raw" switch (so not using the "edd" switch) also seems to work (giving access to or running command.com). I'm also wondering if and how the switches "raw", "bigraw" and "int" relate to "real mode" versus "protected mode" and if the official microsoft 'real mode' patch for dos 8.0 might fix the "deliberate" crash in ME/XP dos that the memdisk page mentions.
Nov
7
comment All FireFTP passwords gone after auto-update
I have accepted your answer because it is indeed the officially documented one (although it didn't help me). Thank you!
Nov
7
revised All FireFTP passwords gone after auto-update
added 131 characters in body
Nov
7
awarded  Commentator
Nov
7
comment All FireFTP passwords gone after auto-update
@Wk_of_Angmar: thank you for the esr tip. Me personally am trying to migrate (what is left to save, since I and my business took multiple BIG (and either expensive or even unrecoverable) hits in data-loss purely thanks to firefox) to palemoon, hopefully that will give me a reliable host-platform for the plugins I rely upon until I find alternatives to migrate the data to.
Nov
7
awarded  Scholar
Nov
7
accepted pxe boot dos 7.x / 8.x on modern mainboard without floppy controller
Nov
7
comment pxe boot dos 7.x / 8.x on modern mainboard without floppy controller
I used "APPEND initrd=DOS.img floppy raw". Removing the raw (for instance replacing it with edd, as you suggested) worked. Even without the "floppy" or "edd" worked in booting MS DOS > 6.22. The base assumption for my question where reports from landesk (for instance, or HP) claiming: "Windows 98 DOS requires a floppy controller." Could you please elaborate and update your answer (for future readers) and maybe explain the difference between: "floppy" "floppy raw" "edd" and "floppy edd". Thank you so much so far !!!
Nov
6
comment pxe boot dos 7.x / 8.x on modern mainboard without floppy controller
did that to and this would have been a great tip, if it worked. Aside from that, when I boot a 6.22 (for instance) using the same syslinux/memdisk combo, the bootdrive (that msdos reports) is A, so that shouldn't be the problem either. If however I plugin a ('golden') usb-floppy drive (empty) dos 7.x/8.x start as normal (and report A as being the boot-drive). The problem lies in the dos-kernel, wanting to do something with a floppy host controller. Pretty sure of that (as other big company's like HP and Landesk confirm). Reproduce it?: take a new notebook, pxe-boot untouched win98 setup image.
Nov
5
comment pxe boot dos 7.x / 8.x on modern mainboard without floppy controller
That is exactly what I am doing. And on every computer in my home that HAS a floppy-host controller (and empty floppy drive) the ms-dos 7.x (or 8.x) image works normally. But on every computer without one (like Dell's zfs server, or any notebook) this same image does not work and renders the (in the question) described error. However when load a ms-dos <= 6.22 (or none ms-dos) image on those machines, they boot normally.
Nov
5
revised All FireFTP passwords gone after auto-update
added 1836 characters in body
Nov
5
revised All FireFTP passwords gone after auto-update
added 67 characters in body
Nov
5
revised All FireFTP passwords gone after auto-update
added 369 characters in body
Nov
5
comment All FireFTP passwords gone after auto-update
I'm sure I'm not the only one that is mad (primarily because of the countless lost hours trying to recover mangled or deleted data due to yet another un-allowed firefox(plugin)-update) about such external decisions that take effect without my consent on MY computer. I know I opened the java-can of worms, Let's close it again. Let's get back to the current actual problem with the fireftp 'up'-date that currently also puts others in the same nasty spot.
Nov
5
comment All FireFTP passwords gone after auto-update
Updates ARE (and where) switched off, also the ones you mentioned. I'm also not the only one who is shure all that crap was turned off, but who where updated (without their concent and somewhere between my bookmarks should be an official mozilla link where it is confirmed there was some kind of hidden 'grace-period' and if you did not voluntarily replaced your good ff3, they did it for you what ever you set or clicked after a certain amount of time). Reading some more on the subject, turns out I'm not the only one that got $%^&* this month with the fireftp update, my current problem is common.
Nov
4
comment pxe boot dos 7.x / 8.x on modern mainboard without floppy controller
If it wasn't enabled, how did I pxe-boot dos 6.22 or the menu-system? :P
Nov
4
comment All FireFTP passwords gone after auto-update
Im actually trying to be polite haha. Wilst I agree that for the average 'young unexperienced internet-user', aka your typical "internet = facebook, youtube and e-banking" they are trying to do some (arguably, since they should leave windows settings alone) good things. But their core-(power)users that have more browsers installed (identity, common browsing, ebanking) and used firefox 3 as a legacy tool to do some work are treated 'not so nice'. No should mean no, and if I need an older java applet to work (in a controlled secure environment) I should be able to unblock it. That's my opinion.